Bug 1269411
| Summary: | [z-stream clone 3.5.6] [vdsm] SpmStart fails after "offline" upgrade of DC with V1 master domain to 3.5 | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | rhev-integ |
| Component: | vdsm | Assignee: | Liron Aravot <laravot> |
| Status: | CLOSED ERRATA | QA Contact: | Aharon Canan <acanan> |
| Severity: | urgent | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 3.5.1 | CC: | acanan, adevolder, ahino, alitke, amureini, bazulay, bugs, ecohen, eedri, fromani, fsimonce, gickowic, gklein, juwu, laravot, lpeer, lsurette, mgoldboi, nlevinki, pkliczew, ratamir, rbalakri, rhodain, sbonazzo, s.kieske, tnisan, ycui, yeylon, ylavi |
| Target Milestone: | ovirt-3.5.6 | Keywords: | Regression, ZStream |
| Target Release: | 3.5.6 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | storage | ||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Previously, upgrading a data center with compatibility version of 3.0 (with a V1 master domain) when it's on maintenance to a compatibility version of 3.5 caused the SPM start to fail. The SPM start in the 3.5 host attempted to inquire the cluster lock and since it is not supported, the SPM failed to start. With this update, SPM start won't fail even if the cluster lock inquiring is not supported.
|
Story Points: | --- |
| Clone Of: | 1242092 | Environment: | |
| Last Closed: | 2015-12-01 20:40:57 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | Storage | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1242092 | ||
| Bug Blocks: | |||
|
Comment 2
Allon Mureinik
2015-10-26 13:41:12 UTC
Can you please add verification steps? Following comment by laravot on August 30 at 16:09:00, 2015 You wrote that there are multiple issues and I am not sure for what issue this bug stands for. Aharon, 1. create a v3.0 dc, add a 3.5 host to it, add a domain..wait for the spm to start. 2. put the dc to maintenance. 3. upgrade the dc to 3.5 4. activate the dc 5. verify that spm start succesfully. you can also test the scenario of the original bug. thanks, Liron. (In reply to Liron Aravot from comment #5) > Aharon, > 1. create a v3.0 dc, add a 3.5 host to it, add a domain..wait for the spm to > start. > 2. put the dc to maintenance. > 3. upgrade the dc to 3.5 > 4. activate the dc > 5. verify that spm start succesfully. > > you can also test the scenario of the original bug. > > thanks, > Liron. Verified using vt18.2 Hi Liron, I'm not sure if I fully understand this bug. I have updated the doc text. Please let me know if you have any feedback. Cheers, Julie Hi Julie, I've updated the doc text. (In reply to Liron Aravot from comment #8) > Hi Julie, > I've updated the doc text. Thanks! Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2015-2530.html |