Bug 907533 - Reports upgrade flag is always present after 3.0 -> 3.1 upgrade
Summary: Reports upgrade flag is always present after 3.0 -> 3.1 upgrade
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine-setup
Version: 3.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
: 3.1.3
Assignee: Alex Lourie
QA Contact: David Botzer
URL:
Whiteboard: integration
Depends On: 895049
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-02-04 16:16 UTC by Idith Tal-Kohen
Modified: 2018-11-30 22:59 UTC (History)
15 users (show)

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.
Clone Of: 895049
Environment:
Last Closed: 2013-03-12 14:29:22 UTC
oVirt Team: ---
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2013:0557 0 normal SHIPPED_LIVE rhevm 3.1.3 bug fix update 2013-03-12 18:26:15 UTC

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
Note You need to log in before you can comment on or make changes to this bug.