Hide Forgot
Description of problem: Many customers are doing "double upgrades" from 3.2 to 3.4. In this process, they are not noticing/following the instructions when upgrading from 3.2/3.3 that upgrade the rhevm-dwh configuration. When they move to 3.4 and they are forced to take rhevm-dwh into consideration, the engine-setup process fails because it cannot understand how to access the ovirt_engine_history database. Version-Release number of selected component (if applicable): rhevm-dwh-3.2.x rhevm-dwh-3.3.x rhevm-dwh-3.4.x How reproducible: 100% Steps to Reproduce: 1. Upgrade rhevm and rhevm-dwh to 3.3 2. Do *not* run rhevm-dwh-setup 3. Upgrade rhevm and rhevm-dwh to 3.4 4. Run engine-setup Actual results: engine-setup fails because it cannot access the dwh database Expected results: The upgrade process can move from a 3.2 configuration to a 3.4 configuration. Additional info: Fixing this situation is quite painful. Multiple downgrades of rhevm-dwh are required, as well as manual changes to the engine database to "trick" dwh into upgrading its DB schema. Taken in conjunction with reports, it is a very involved process.
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 ***