Hi, I think you are facing the same problem I had when I did the update, LVM filter has been deactivated and replaced with a file a devices file in /etc/lvm/devices/system.devices if you cat that file you'll find only the OS lvm, you have to add the devices that contain you gluster VGs to that file using lvmdevices --adddev /dev/sdb for example, you have to know the name and path of the devices that contain you gluster VGs. https://man7.org/linux/man-pages/man8/lvmdevices.8.html Regards. On Wed, Jun 22, 2022, 18:24 <simon@justconnect.ie> wrote:
I upgraded the Engine first and then tried one of the 3 nodes via the Manager WebUI.
On reboot the node boots straight into emergency mode having timed out on the gluster volumes:
Timed out waiting for device dev-disk-by\....... Dependency failed for /gluster_bricks/engine
Same messages for vmstore and data01
If I edit /etc/fstab and comment out the gluster entries it boots into the oVirt node.
The gluster pv is also not there:
PV VG Fmt Attr PSize PFree /dev/sda3 ovirt_vg_sda lvm2 a-- <445.04g 21.48g
Whereas the other 2 nodes have the following:
PV VG Fmt Attr PSize PFree /dev/sda3 ovirt_vg_sda lvm2 a-- <445.04g 21.48g /dev/sdb gluster_vg_sdb lvm2 a-- <893.25g 0
Simon... _______________________________________________ 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/K26IEUYP6XFJCF...