Hi,
we have mentioned several times that it doesn't make sense to oVirt on a
single host setup. So you really need to add 2nd host to your setup, move
the 1st host to Maintenance and execute Enroll certificates.
Regards,
Martin
On Sun, Oct 4, 2020 at 5:30 PM <thomas(a)hoberg.net> wrote:
From what I observed (but it's not something I try often), if you
try to
enable maintenance on a host and have VMs on it, it will try migrating the
VMs first, which is a copy-first, state-transfer-afterwards process. So if
there is no migration target available or if the copying and state-transfer
fail, the VM will simply continue to run on the original host... and the
host will refuse to go into maintenance.
It doesn't solve your problem, but the loss of service you fear shouldn't
happen either... except sometimes oVirt seems to have bugs or the resulting
network activity cause confusion.
Ah, perhaps this is important: I've only ever tried that by setting a host
into maintenance (typically for patch updates) via the GUI. I am far less
convinced that VM migration would also be triggered if you use the
'hosted-engine --set-maintenance --mode=local' variant on the host that
runs the HostedEngine VM. That might just make it unavailable for newly
started VMs.
_______________________________________________
Users mailing list -- users(a)ovirt.org
To unsubscribe send an email to users-leave(a)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/7D6XC4YHIKM...
--
Martin Perina
Manager, Software Engineering
Red Hat Czech s.r.o.