Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 907533

Summary:	Reports upgrade flag is always present after 3.0 -> 3.1 upgrade
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Idith Tal-Kohen <italkohe>
Component:	ovirt-engine-setup	Assignee:	Alex Lourie <alourie>
Status:	CLOSED ERRATA	QA Contact:	David Botzer <dbotzer>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	3.1.0	CC:	acathrow, alourie, bazulay, cpelland, dyasny, hambrose, iheim, mgoldboi, nigjones, perobins, pstehlik, pzhukov, Rhev-m-bugs, sgrinber, ykaul
Target Milestone:	---	Keywords:	ZStream
Target Release:	3.1.3
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	integration
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Previously, the upgrade flag was constantly present after upgrading from Red Had Enterprise Virtualization Manager 3.0 to 3.1. This prevented installing reports from scratch in the upgraded system. Now, the upgrade flag is not constantly present.	Story Points:	---
Clone Of:	895049	Environment:
Last Closed:	2013-03-12 14:29:22 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:
Bug Depends On:	895049
Bug Blocks:

Comment 2 David Botzer 2013-02-07 12:56:59 UTC

I would like to know where is this flag ? the location / file

I wanna examine it when I have report on rhevm30 & withouth reports

And if the location is the same when I upgrade to rhevm3.1 ? 

Which 3.1 build should I upgrade to ? 26.1 ?

Comment 4 David Botzer 2013-02-10 11:57:30 UTC

Fixed, 3.1/si27
rhevm30 without reports, or dwh
After yum update rhevm-setup, i examined /etc/ovirt-engine and it was correct.
I upgraded to si27 and all is correct
Fixed, 3.1/si27

Comment 6 errata-xmlrpc 2013-03-12 14:29:22 UTC

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.

http://rhn.redhat.com/errata/RHBA-2013-0557.html