Description of problem: Upgrade on latest rhel 7.2 vdsm-python-4.16.29-1.el7ev.noarch to vdsm-4.17.10.1-0.el7ev.noarch fails , because of passwd module. From syslog: Nov 19 10:32:02 cheetah01 vdsmd_init_common.sh: Modules passwd, configfile are not configured I can see that in host there is: /usr/sbin/sasldblistusers2 -f /etc/libvirt/passwd.db vdsm@rhevh but from what I understand vdsm-4.17.10.1 checks for vdsm@ovirt. Version-Release number of selected component (if applicable): vdsm-python-4.16.29-1.el7ev.noarch How reproducible: always Steps to Reproduce: 1. Install vdsm-python-4.16.29-1 2. Upgrade to vdsm-4.17.10.1-0 Actual results: Fail: Modules passwd, configfile are not configured Expected results: Success Additional info:
Also note - The only way I could reproduce, is from 3.6 engine via UpgradeManager feature. I couldn't reproduce with 3.5 engine and 'reinstall' feature. Could be related to issue.
(In reply to Ondra Machacek from comment #1) > Also note - The only way I could reproduce, is from 3.6 engine via > UpgradeManager feature. I couldn't reproduce with 3.5 engine and 'reinstall' > feature. Could be related to issue. Upgrade Manager feature is wide description - did you mean clicking on 'Upgrade' button and later on submitting the dialog?
IIUC the host had to be in 3.5 cluster level cluster in 3.6 engine as vdsm-4.16 is for RHEL 6. Am I right?
(In reply to Jiri Belka from comment #2) > Upgrade Manager feature is wide description - did you mean clicking on > 'Upgrade' button and later on submitting the dialog? Yes. Just hit upgrade button and wait for fail. (In reply to Jiri Belka from comment #3) > IIUC the host had to be in 3.5 cluster level cluster in 3.6 engine as > vdsm-4.16 is for RHEL 6. Am I right? The cluster is 3.5. Engine is 3.6. And host is latest el7.
I believe that v4.17.10-20-g365b214 https://gerrit.ovirt.org/48222 (still unbuilt) solves this bug.
I don't know the release process of vdsm, but I believe, this should be ON_QA, as vdsm-4.17.11-0.el7ev.noarch provides bug fix, no?
>> > Upgrade Manager feature is wide description - did you mean clicking on >> > 'Upgrade' button and later on submitting the dialog? >> >> Yes. Just hit upgrade button and wait for fail. >> >> [..] >> >> The cluster is 3.5. Engine is 3.6. And host is latest el7. > I believe that v4.17.10-20-g365b214 https://gerrit.ovirt.org/48222 > (still unbuilt) solves this bug. I could not reproduce with 'Upgrade' button for a RHEL 7.2 host with vdsm-4.16.30-1.el7ev.x86_64, it upgraded successfully to vdsm-4.17.11-0.el7ev.noarch (host part of 3.5 cluster in rhevm-3.6.1-0.2.el6.noarch engine).
(In reply to Ondra Machacek from comment #6) > I don't know the release process of vdsm, but I believe, this should be > ON_QA, as vdsm-4.17.11-0.el7ev.noarch provides bug fix, no? Correct.
Upgrade from vdsm-4.16.30-1.el7ev to vdsm-4.17.12-0.el7ev succeed.
According to verification status and target milestone this issue should be fixed in oVirt 3.6.1. Closing current release.