Hello again,
to answer your question, how did I make a clean install and reintegrate the node in the
cluster? Maybe my approach was a bit awkward/inconvenient, but this is what I did:
- Install CentOS 8
- Install oVirt Repository and packages: cockpit-ovirt-dashboard, vdsm-gluster,
ovirt-host
- Remove the Gluster bricks of the old node from the data/engine/vmstore volumes
- Process a single cluster node installation on the new node via the oVirt Dashboard, in
order to setup Gluster and the bricks (hosted-engine setup was skipped)
- On the new node: Delete the vmstore/engine/data volumes and the file metadata in the
bricks folder
- Added the bricks to the volumes of the existing cluster again
- Added the host to the cluster
Would you suggest a better approach to setup a new node for an existing cluster?
At this point I'm not sure if I just overlooked the "hosted engine deployment
action" when I've added the new host. Unfortunately I cannot try to edit the host
anymore since my colleague did another reinstall of the node.
Thanks so far and greetings,
Marcus
-----Ursprüngliche Nachricht-----
Von: Yedidyah Bar David <didi(a)redhat.com>
Gesendet: Montag, 14. September 2020 10:56
An: Rapsilber, Marcus <Marcus.Rapsilber(a)isotravel.com>
Cc: users <users(a)ovirt.org>
Betreff: Re: [ovirt-users] Enable a cluster node to run the hosted engine
On Mon, Sep 14, 2020 at 11:18 AM <rap(a)isogmbh.de> wrote:
Hi there,
currently my team is evaluating oVirt and we're also testing several fail scenarios,
backup and so on.
One scenario was:
- hyperconverged oVirt cluster with 3 nodes
- self-hosted engine
- simulate the break down of one of the nodes by power off
- to replace it make a clean install of a new node and reintegrate it
in the cluster
How exactly did you do that?
Actually everything worked out fine. The new installed node and related bricks (vmstore,
data, engine) were added to the existing Gluster storage and it was added to the oVirt
cluster (as host).
But there's one remaining problem: The new host doesn't have the grey crown,
which means it's unable to run the hosted engine. How can I achieve that?
I also found out that the ovirt-ha-agent and ovirt-ha-broker isn't started/enabled on
that node. Reason is that the /etc/ovirt-hosted-engine/hosted-engine.conf doesn't
exist. I guess this is not only a problem concerning the hosted engine, but also for HA
VM's.
When you add a host to the engine, one of the options in the dialog is to deploy it as a
hosted-engine.
If you don't, you won't get this crown, nor these services, nor its status in
'hosted-engine --vm-status'.
If you didn't, perhaps try to move to maintenance and reinstall, adding this option.
If you did choose it, that's perhaps a bug - please check/share relevant logs (e.g. in
/var/log/ovirt-engine, including host-deploy/).
Best regards,
Thank you for any advice and greetings, Marcus
_______________________________________________
Users mailing list -- users(a)ovirt.org
To unsubscribe send an email to users-leave(a)ovirt.org Privacy
Statement:
https://protection.retarus.com/v1?u=https%3A%2F%2Fwww.ovirt.org%2Fpriv
acy-policy.html&c=3ilYjgr&r=338RVlOwLz6SWhhP16s8RO&k=7s1&s=i9ZtAxZ4Hjh
a7cyQljzYgZoSsOuJ5qnJkh0cU75rfgL oVirt Code of Conduct:
https://protection.retarus.com/v1?u=https%3A%2F%2Fwww.ovirt.org%2Fcomm
unity%2Fabout%2Fcommunity-guidelines%2F&c=3ilYjgr&r=5VIqhyv90pUj07OGZz
9qix&k=7s1&s=UiOTbmf9BSOB46ff91IjO7G8dkMWHzi2GOIcveqAySn
List Archives:
--
Didi