All vdsm CI runs fails now due to: https://bugzilla.redhat.com/2025527 Looks like leftover configuration (locking_type=4) from rhel 7 that was useless but harmless on rhel 8 is harmful now, converted by lvm to --readonly, which breaks lvchange --refresh. So far seen only in vdsm CI, using Centos Stream. It is likely to break also on a real system using the same lvm version (unknown yet). I posted this to log lvm version: https://gerrit.ovirt.org/c/vdsm/+/117741

On Mon, Nov 22, 2021 at 3:36 PM Nir Soffer <nsoffer(a)redhat.com&gt; wrote: > >> On Mon, Nov 22, 2021 at 3:23 PM Nir Soffer <nsoffer(a)redhat.com&gt; wrote: >> >> All vdsm CI runs fails now due to: >> https://bugzilla.redhat.com/2025527 >> >> Looks like leftover configuration (locking_type=4) from rhel 7 that >> was useless but harmless >> on rhel 8 is harmful now, converted by lvm to --readonly, which breaks >> lvchange --refresh. >> >> So far seen only in vdsm CI, using Centos Stream. It is likely to >> break also on a real system >> using the same lvm version (unknown yet). >> >> I posted this to log lvm version: >> https://gerrit.ovirt.org/c/vdsm/+/117741 > > Checking the code shows that this happens only when using read only mode - this > is leftover from rhel 7 and never used in rhel 8. The failure is only > in vdsm tests > testing read only mode. This should unbreak the CI: https://gerrit.ovirt.org/c/vdsm/+/117743

More work is needed to remove the legacy read-only mode form lvm module. Nir