I deployed Ovirt on a single node to test the operation of glusterfs (Single node HCI). After deploying, I got a single volume consisting of one bricks in "distributed" mode

I am interested in why brick does not come up after a host reboot. I have not focused on fault tolerance yet.After a reboot I have to turn off and on volume, then, all starts working. In my opinion this should happen automatically but it doesn't. This also happens if you use a volume with replication

Did your host crash ? When the host crashes the VG might not get activates , or the VDO service might still be recovering when the LVM is trying to start your LVs. It rarely happens that the brick doesn't start but the Filesystem is mounted and Glusterd has been started. Best Regards, Strahil Nikolov В сряда, 21 юли 2021 г., 10:31:59 ч. Гринуич+3, Patrick Lomakin <patrick.lomakin(a)gmail.com&gt; написа: For a long time I have been seeing the same error, which cannot be corrected.After restarting the host which has a Volume of one or more Bricks, the Volume starts with the status "Online", but the Bricks remain "Offline". This leads to having to manually restart Volume, the ovirt-ha and ovirt-broker services, and run the hosted-engine --connect-storage command. And only after that I can start the hosted engine back to normal. I tried this on different server hardware and different operating systems for the host, but the result is the same. This is a very serious flaw that nullifies the high availability in HCI using GlusterFS.Regards! _______________________________________________ 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/O6LA5WAZPQD...