Furthermore, you should have a version requested by vdsm-tool configure. If there is an old version, the config should update the file. Having a higher version shouldn't be possible unless you modified it manually: In such a case, you should place "# VDSM PRIVATE" into the config, which means you should maintain it.
This one is not recommended, as there can be some new config that has no support in old code and can lead it to misbehave. *Regards,* *Shani Leviim* On Tue, Feb 2, 2021 at 12:19 PM Shani Leviim <[email protected]> wrote: > 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/multipath.py > > 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 <[email protected]> > 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 -- [email protected] >> To unsubscribe send an email to [email protected] >> 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/[email protected]/message/SEZI5V5RVPKMAHMWS565G36JV6LD62YN/ >> >
_______________________________________________ Users mailing list -- [email protected] To unsubscribe send an email to [email protected] 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/[email protected]/message/EWZBCVHE3C7O5XDVOMNIUIIQLO5DI26S/
