Hi Gianluca, The VDSM REVISION value doesn't depend on the oVirt/RHV version, but it's the last value in your lib/vdsm/tool/configurators/multipath.py: https://github.com/oVirt/vdsm/blob/master/lib/vdsm/tool/configurators/mul... The value is being increased whenever we change the multipath config, so you can see the latest version. This number is not related to the cluster version or vdsm version directly. By using a different revision number, you may not include the changes in the multipath config, which came along with those versions. *Regards,* *Shani Leviim* On Tue, Feb 2, 2021 at 10:51 AM Gianluca Cecchi <gianluca.cecchi(a)gmail.com&gt; wrote: > Hello, > considering that the best practice is to keep the multipath.conf file > unmodified, is there a table with the mapping between the version of > oVirt/RHV and the value of "VDSM REVISION" in /etc/multipath.conf, so that > in case of doubts one can crosscheck (eg inherited environment where > different admins were managing...)? > > Does this value depend only on the hypervisor installed sw version or > also on the Cluster Compatibility version of the cluster the host belongs > to, or on the engine version? > > In several oVirt/RHV environments with 4.3 / 4.4 I see several numbers > for the VDSM REVISION from 2.0, to 1.9 and 1.5... > > Also what could be the impact of having a wrong (higher or lower) > revision inside the file? > > Thanks, > Gianluca > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)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/SEZI5V5RVPK... >