Are you making sure to reboot the hosts via the oVirt engine?
What I tend to do is put the host into maintenance mode, login and reboot it, once I know
it's up I take it out of maintenance mode.
It's not good to reboot a host while it's active from its terminal you will have
issues/risks with services not stopping, so you need to do it from the engine or by
putting it into maintenance mode first.
I've had issues with the engine detecting the host is back up after a reboot and
taking ages, so I tend to stick them into maintenance mode and reboot from the terminal.
Otherwise no, it reboots normally for me.
From: Peter H <peter(a)hashbang.org>
Sent: 27 February 2023 13:15
To: users <users(a)ovirt.org>
Subject: [ovirt-users] Re: Very long reboot times of "RH" hosts with oVirt
Peter H <peter(a)hashbang.org>
2:04 PM (0 minutes ago)
Sorry, my mail got sent before it was ready, so I try again ;-)
I was just wondering if anyone else is experiencing the following issue.
On both real physical machines and on VM where I have installed a RH derivative like
CentOS, CentOS Stream, Rocky Linux or Alma Linux the reboot times are initially normal.
After installation of oVirt and all the dependencies the reboot
(shutdown) increases to anywhere between 3 and 5 minutes.
If I disable and stop the service wdmd.service reboot time is normal but after reboot the
service is enabled again.
I have then masked the watchdog service and then reboot times are normal every time.
But I noticed that masking the watchdog service on a "Silver crown"
caused the "Hosted Engine HA" functionality to fail and the host lost its engine
Is it safe to mask wdmd.service on normal hosts?
Can the reboot times be decreased on hosted engine hosts without breaking HA?
Users mailing list -- users(a)ovirt.org
To unsubscribe send an email to users-leave(a)ovirt.org Privacy Statement:
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/