Another workaround that comes to my mind: disable server quorum gluster option. Of course all of these are just workarounds and not a real fix. Best Regards,Strahil Nikolov On Mon, Apr 19, 2021 at 13:43, Thomas Hoberg<[email protected]> wrote: Well, that's why I really want a theory of operation here, because removing a host as a gluster peer might just break something in oVirt... And trying to fix that may be not trivial either.
It's one of those cases where I'd just really love to have nested virtualization work better so I can snapshot an virtualized HCI cluster before I do these things, so I can revert with a click or three. And what really irritates me is that even hosts that do not contribute bricks to a volume show up when I do a volume status. Mostly because I've had situations where I had the typical 3 node HCI with an additional 5 compute-only nodes and when I was updating these with some degree of overlap (several unloaded hosts at once), all of a sudden vmstore/data/engine would go down for lack of quorum.... just because non-participating hosts were not available!! So again, if one of the oVirt developers could shine a light into this, it would be very much appreciated. _______________________________________________ Users mailing list -- [email protected] To unsubscribe send an email to [email protected] 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/[email protected]/message/QPARRXAVKOTP4JFZGHVOKLKVRHFI4LL4/
_______________________________________________ Users mailing list -- [email protected] To unsubscribe send an email to [email protected] 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/[email protected]/message/RHM2KNUN3TDZJKPVRMJU7PCLPNOUCQPX/
