You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
/etc/lvm/lvmlocal.conf is installed by vdsm-tool configure --module lvm.
However vdsm-tool config-lvm-filter is run before the configuration phase,
and it run before since we must setup multipath blacklist before configuring
vdsm.
This means that when configuring lvm devices on ovirt < 4.5.1, the option multipath_wwids_file = "" is not applied, and lvm may fail to add some
devices to the devices file.
We don't have a way to fix this in 4.5.1.
When upgrading 4.5.1 to 4.5.2 the configuration is already available, no issue.
When upgrading from version < 4.5.1 to version >= 4.5.2, we can fix the issue by forcing this option in vdsm-tool --config:
Another way to fix this is to eliminate vdsm-tool config-lvm-filter and move the
configuration step to vdsm-tool configure --module lvm. But this requires enforcing
order of configurators in vdsm-tool (e.g. lvm runs before multipath), or merging the
storage configurators to one module (storage?).
/etc/lvm/lvmlocal.conf
is installed byvdsm-tool configure --module lvm
.However
vdsm-tool config-lvm-filter
is run before the configuration phase,and it run before since we must setup multipath blacklist before configuring
vdsm.
This means that when configuring lvm devices on ovirt < 4.5.1, the option
multipath_wwids_file = ""
is not applied, and lvm may fail to add somedevices to the devices file.
We don't have a way to fix this in 4.5.1.
When upgrading 4.5.1 to 4.5.2 the configuration is already available, no issue.
When upgrading from version < 4.5.1 to version >= 4.5.2, we can fix the issue by forcing this option in vdsm-tool --config:
Another way to fix this is to eliminate
vdsm-tool config-lvm-filter
and move theconfiguration step to
vdsm-tool configure --module lvm
. But this requires enforcingorder of configurators in vdsm-tool (e.g. lvm runs before multipath), or merging the
storage configurators to one module (storage?).
The ideal order:
Related bugs:
The text was updated successfully, but these errors were encountered: