On Wed, 1 Sep 2021, Nir Soffer wrote:
This is a pretty major issue since we can no longer create new VMs. As a workaround, I could change the mount path of the volume to only reference a single IP, but oVirt won't let me edit the mount. I wonder if I could manually edit in the database, then reboot the hosts one by one to make the change take effect without having to shut down hundreds of VMs at once?
This should work.
I tried editing the database to point to a single IP and it works, I'm able to mount it and create disks on it. However, attempts to migrate any live VMs between a system with the old mount and one with the new mount fail, presumably because the mountpoint is now named differently. I believe doing this would effectively split my cluster into hosts on two separate storage pools. I wonder if there's some way to force the mount name to be the same?