Bug 1283597
| Summary: | upgrade vdsm-python-4.16.29-1 to vdsm-4.17.10.1-0 fails, because of passwd module | ||
|---|---|---|---|
| Product: | [oVirt] vdsm | Reporter: | Ondra Machacek <omachace> |
| Component: | Tools | Assignee: | Yaniv Bronhaim <ybronhei> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Ondra Machacek <omachace> |
| Severity: | urgent | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 4.17.10 | CC: | bugs, danken, gklein, jbelka, ybronhei, ykaplan |
| Target Milestone: | ovirt-3.6.1 | Flags: | gklein:
ovirt-3.6.z?
gklein: blocker? rule-engine: planning_ack? danken: devel_ack+ rule-engine: testing_ack+ |
| Target Release: | 4.17.11 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | infra | ||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-12-16 12:17:52 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | Infra | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1285700 | ||
|
Description
Ondra Machacek
2015-11-19 11:30:50 UTC
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. |