Brief background: Simple environment -- self-hosted engine and two oVirt Node hosts all running 4.4.4. Couple NFS-based data storage domains and a few VLAN-based networks. Upgrading the Hosted Engine from 4.4.4 to 4.4.8 appears to have completed successfully and without incident. I followed the published instructions. :) Problems upgrading the oVirt Node hosts !!! Initialized cluster upgrade. It got as far as rebooting the first host. ERRORS. Said "vdsmd... BAD" Found journal log entry suggesting I run a vdsm config command. Did that and rebooted. VDSM error went away and all looked good. Unfortunately VMs started on that host now were clearly unstable. Ugh! Unusable host. Removed that host from the cluster. Reinstalled from scratch using the 4.4.8 ISO. All went well. Added it to the cluster and deployed the HE to it. No Errors. Unfortunately, it is now stuck in a NonOperational state and I cannot determine why. Please help.
You can now discard this thread !!! Prior to creating this thread, I also tried to copy the networks from another functioning host thinking that might be needed. Did not get any errors for the copy function, but the networks were not copied. That's when started this thread. Since then, I said, "fck it" and decided to try something while waiting for help. I manually added the networks to the rebuilt host. Suddenly (and apparently magically) it is now in Up state.
In case you decide to try again or for other oVirt users, who see similar issues.... When 'required' networks for the cluster aren't there, or shared storage is unreachable, the host is put into non-operational state. oVirt engine wants to handle the network configs for the hypervisors. The required networks should be configured in the engine's "setup host networks" for the new host. When you add a new hypervisor host to the oVirt cluster, by default it doesn't set up 'required networks', and doing things behind the engine's back isn't a good idea because it doesn't know which logical network should be connected to which network interface. If you forget to tell your shared storage to allow access from the new host it will also cause non-operational state. On Wed, Sep 15, 2021 at 3:32 PM Diggy Mc <d03@bornfree.org> wrote:
You can now discard this thread !!!
Prior to creating this thread, I also tried to copy the networks from another functioning host thinking that might be needed. Did not get any errors for the copy function, but the networks were not copied.
That's when started this thread.
Since then, I said, "fck it" and decided to try something while waiting for help.
I manually added the networks to the rebuilt host. Suddenly (and apparently magically) it is now in Up state. _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/EZSSMERYDSUS25...
participants (2)
-
Diggy Mc -
Edward Berger