Bug 1150545
Summary: | [RHEVM-SETUP] - Upgrade instruction are provided at the end of clean install | ||
---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | rhev-integ |
Component: | rhevm-setup-plugins | Assignee: | Yedidyah Bar David <didi> |
Status: | CLOSED ERRATA | QA Contact: | Petr Matyáš <pmatyas> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.4.0 | CC: | bazulay, bkorren, dfediuck, didi, ecohen, gklein, iheim, juwu, lsurette, pmatyas, pstehlik, rbalakri, Rhev-m-bugs, sbonazzo, sherold, sradco, talayan, tdosek, yeylon, ylavi |
Target Milestone: | --- | Keywords: | ZStream |
Target Release: | 3.4.3 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | integration | ||
Fixed In Version: | org.ovirt.engine-root-3.4.3-2 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | 1098191 | Environment: | |
Last Closed: | 2014-10-23 12:19:53 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1098191 | ||
Bug Blocks: | 1126430 |
Comment 2
Petr Matyáš
2014-10-13 12:56:33 UTC
This bug was fixed in rhevm-setup-plugins, so why is the component is on engine? ovirt-engine-restapi? this causes this bug to be added to 2 erratas - something which isn't possible. so either this bug shouldn't have been added to the rhevm-setup-plugins errata, or the component should changed to rhevm-setup-plugins. please advise. Would be enough to test the 3.5 clone of this bug and if it passes put verify on this one too or do you want some special test cases? Barak: Setting component to rhevm-setup-plugins, where the main change was done. Engine was updated too, to require this version of rhevm-setup-plugins. The real bug is in dwh/reports, we decided to "fix" it by changing rhevm-setup-plugins. Petr: The bug (and fix) is related to relevant upgrade flows. Since there is more than one flow, you'll have to consider flows with the fix in the 3.5 bug but without the fix in this (3.4) bug. How exactly you document what you test is less important for me. The main fix for 3.4, which was on trying to upgrade from 3.2, you seem to have already verified (in the 3.5 bug 1098191 comment 15), so it should be ok still. Just in case please verify that too, to make sure we did not break that path. Hi Didi, Can you provide the doc text info for this bug please? Cheers, Julie This bug was meant to prevent something like bug 1123751 for 3.3->3.5. I am not sure we prevented all possible such flows, and even if we didn't, it should still work, unlike 3.2->3.4. We just did not want to have to test/support this. 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/RHEA-2014-1710.html |