Bug 971346 - Rhevm-setup misguides user with regards to steps for rhevm-reports upgrade
Summary: Rhevm-setup misguides user with regards to steps for rhevm-reports upgrade
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine-setup
Version: 3.2.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 3.3.0
Assignee: Sandro Bonazzola
QA Contact: Lukas Svaty
URL:
Whiteboard: integration
: 967721 (view as bug list)
Depends On:
Blocks: 902971 973239
TreeView+ depends on / blocked
 
Reported: 2013-06-06 10:26 UTC by Tomas Dosek
Modified: 2018-12-02 17:11 UTC (History)
11 users (show)

Fixed In Version: is2
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 973239 (view as bug list)
Environment:
Last Closed: 2014-01-21 17:26:32 UTC
oVirt Team: ---
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 392313 0 None None None Never
Red Hat Product Errata RHSA-2014:0038 0 normal SHIPPED_LIVE Important: Red Hat Enterprise Virtualization Manager 3.3.0 update 2014-01-21 22:03:06 UTC
oVirt gerrit 15539 0 None None None Never

Description Tomas Dosek 2013-06-06 10:26:41 UTC 
Description of problem:
Rhevm-setup misguides user with regards to steps for rhevm-reports upgrade

The script shows following instructions:

* Perform the following steps to upgrade the history service or the reporting package:
1. Execute: yum update ovirt-engine-reports*
2. Execute: ovirt-engine-dwh-setup
3. Execute: ovirt-engine-reports-setup


For RHEV-M this should be rebranded in the same way packages are.


Version-Release number of selected component (if applicable):
GA candidate sf17.3

How reproducible:
100%

Steps to Reproduce:
1. Have a 3.1 setup with reports and dwh installed
2. Upgrade the setup


Actual results:
The upgrade script misguides users

Expected results:
All ovirt-engine should be replaced by rhevm in the strings displayed to users
Comment 7 Moran Goldboim 2013-06-12 20:49:48 UTC 
*** Bug 967721 has been marked as a duplicate of this bug. ***
Comment 8 Lukas Svaty 2013-06-27 15:31:38 UTC 
verified in is3
Comment 9 Charlie 2013-11-28 00:18:26 UTC 
This bug is currently attached to errata RHEA-2013:15231. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag.

Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information:

* Cause: What actions or circumstances cause this bug to present.
* Consequence: What happens when the bug presents.
* Fix: What was done to fix the bug.
* Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore')

Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug.

For further details on the Cause, Consequence, Fix, Result format please refer to:

https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes 

Thanks in advance.
Comment 10 Sandro Bonazzola 2013-12-20 07:36:31 UTC 
I don't think this change needs to be documented.
Comment 12 errata-xmlrpc 2014-01-21 17:26:32 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/RHSA-2014-0038.html
Note You need to log in before you can comment on or make changes to this bug.