Bug 1129794

Summary:	Provide a method to upgrade reports from more than just the previous version
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	James W. Mills <jamills>
Component:	ovirt-engine-reports	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, bazulay, didi, ecohen, iheim, Rhev-m-bugs, yeylon
Target Milestone:	---
Target Release:	3.4.1
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 09:18:45 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:00:04 UTC

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-reports configuration.

When they move to 3.4 and they are forced to take rhevm-reports into consideration, the engine-setup process fails because it cannot understand how to access the rhevmreports database.


Version-Release number of selected component (if applicable):

rhevm-reports-3.2.x
rhevm-reports-3.3.x
rhevm-reports-3.4.x

How reproducible:

100%

Steps to Reproduce:
1. Upgrade rhevm and rhevm-reports to 3.3
2. Do *not* run rhevm-reports-setup
3. Upgrade rhevm and rhevm-reports to 3.4
4. Run engine-setup

Actual results:

engine-setup fails because it cannot access the reports 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-reports/jasper are required.  Taken in conjunction with dwhd, it is a very involved process.

Comment 2 Yedidyah Bar David 2014-08-14 09:18:45 UTC

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 ***