Hi Adam,
Le 04/10/2017 à 16:48, Adam Litke a écrit :
> Sure. vdsm-tool should be disabling lvmetad on the host automatically.
> Maybe some of the hosts were fresh installed and others have been
> upgraded from older versions? In any case, you should be able to run on
> any host in maintenance mode:
>
> sudo vdsm-tool configure --force
>
> And this should edit the lvm.conf file to disable lvmetad globally and
> also prevent the lvmetad service from starting.
Sorry, but nope.
# vdsm-tool configure --force
Checking configuration status...
Current revision of multipath.conf detected, preserving
libvirt is already configured for vdsm
SUCCESS: ssl configured to true. No conflicts
Running configure...
Reconfiguration of sebool is done.
Reconfiguration of libvirt is done.
Done configuring modules to VDSM.
# grep use_lvmetad /etc/lvm/lvm.conf |grep -v '#'
use_lvmetad = 1
vdsm-tool disables lvmetad in the local lvm config (/etc/lvm/lvmlocal.conf) which is owned now by vdsm, similar to the way multipath configuration is managed by vdsm.
Actually, as you found a workaround, it's not a big deal, especially if
this point has been fixed in version greater than 3.6.7.
But this was added in 4.0.7.
You should upgrade to 4.1, including many other features and fixes.
Nir