On Tue, Sep 15, 2020 at 2:40 PM Rapsilber, Marcus <Marcus.Rapsilber@isotravel.com> wrote:
I'm not sure if this log files tells anything about the problem why the node "ipc3.dc" isn't capable to run the hosted engine. Today we tried the whole procedure again. But this time we didn't install the new node via single node cluster setup. It was a manual setup of the cluster storage. When we've added the host ("New Host") we made sure that "Hosted engine deployment action" was set to "deploy". Nevertheless we're still not able to allow the new node to run the hosted engine. The grey crown is missing.
What's the output of 'hosted-engine --vm-status' on this host, and on other hosts (that are ok)?
What is the criteria for a host to be able to run the hosted engine? Is some special service required? Do we have to install another package? Or is there an Ansible script that does the required setup?
Generally speaking, it should be fully automatic, if you mark the checkbox in "Add host", and AFAICT, the log you attached looks ok. Also: - The host needs to be in the same DC/cluster, needs to have access to the shared storage, etc. You can try to start the services manually, if they are not up: systemctl status ovirt-ha-broker ovirt-ha-agent systemctl start ovirt-ha-broker ovirt-ha-agent - and/or check their logs, in /var/log/ovirt-hosted-engine-ha . Best regards,
Thanks and greetings Marcus
-----Ursprüngliche Nachricht----- Von: Yedidyah Bar David <didi@redhat.com> Gesendet: Dienstag, 15. September 2020 09:33 An: Rapsilber, Marcus <Marcus.Rapsilber@isotravel.com> Cc: users <users@ovirt.org> Betreff: Re: [ovirt-users] Enable a cluster node to run the hosted engine
On Tue, Sep 15, 2020 at 10:10 AM Rapsilber, Marcus <Marcus.Rapsilber@isotravel.com> wrote:
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?
Sorry, I have no experience with gluster, so can't comment on your particular steps, although they sound reasonable. the main missing thing is enabling hosted-engine when adding the host to the engine.
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.
Very well.
If this happens again, please tell us.
Best regards,
Thanks so far and greetings, Marcus
-----Ursprüngliche Nachricht----- Von: Yedidyah Bar David <didi@redhat.com> Gesendet: Montag, 14. September 2020 10:56 An: Rapsilber, Marcus <Marcus.Rapsilber@isotravel.com> Cc: users <users@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@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@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://protection.retarus.com/v1?u=https%3A%2F%2Fwww.ovirt.org%2Fpr iv acy-policy.html&c=3ilYjgr&r=338RVlOwLz6SWhhP16s8RO&k=7s1&s=i9ZtAxZ4H jh a7cyQljzYgZoSsOuJ5qnJkh0cU75rfgL oVirt Code of Conduct: https://protection.retarus.com/v1?u=https%3A%2F%2Fwww.ovirt.org%2Fco mm unity%2Fabout%2Fcommunity-guidelines%2F&c=3ilYjgr&r=5VIqhyv90pUj07OG Zz 9qix&k=7s1&s=UiOTbmf9BSOB46ff91IjO7G8dkMWHzi2GOIcveqAySn List Archives:
-- Didi
-- Didi
-- Didi