Bug 1129797
Summary: | Provide a method to upgrade dwh from more than just the previous version | ||
---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | James W. Mills <jamills> |
Component: | ovirt-engine-dwh | Assignee: | Shirly Radco <sradco> |
Status: | CLOSED DUPLICATE | QA Contact: | Pavel Stehlik <pstehlik> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 3.4.1-1 | CC: | acathrow, ecohen, iheim, Rhev-m-bugs, yeylon |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | integration | ||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2014-08-14 10:13:26 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
James W. Mills
2014-08-13 17:06:33 UTC
Note that the manual database changes are only required if engine-setup was run prior to upgrading rhevm-dwhd, which reslults in a fully functional 3.4 engine database, with an updated minimumETL variable. Thanks! ~james Please see https://bugzilla.redhat.com/show_bug.cgi?id=1111749#c19 for a workaround. The fix in bug #1123751 which will be included in 3.4.2 will make engine-setup refuse to upgrade the engine to 3.4 if dwh/reports 3.2 are found. Users that already upgraded the engine to 3.4.{0,1} will have to use the above workaround. If they still have engine 3.3 they'll simply have to upgrade dwh and reports to 3.3 too before upgrading the engine to 3.4. *** This bug has been marked as a duplicate of bug 1123751 *** |