Bug 990942 - [rhevm-reports] - reports setup fails after running otopi engine setup
[rhevm-reports] - reports setup fails after running otopi engine setup
Status: CLOSED ERRATA
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine-reports (Show other bugs)
3.3.0
x86_64 Linux
unspecified Severity high
: ---
: 3.3.0
Assigned To: Sandro Bonazzola
Barak Dagan
infra
:
: 992998 998391 (view as bug list)
Depends On:
Blocks: 1019461
  Show dependency treegraph
 
Reported: 2013-08-01 05:11 EDT by Yaniv Lavi
Modified: 2016-02-10 14:32 EST (History)
8 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Previously, rhevm-reports could not be installed after using otopi to set up the manager. This has now been fixed, and rhevm-reports can be set up as expected.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2014-01-21 09:55:46 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: Infra
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Yaniv Lavi 2013-08-01 05:11:28 EDT
Description of problem:
reports setup fails after running otopi engine setup

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

How reproducible:
Always

Steps to Reproduce:
1. run otopi based engine setup
2. try to install reports setup

Actual results:
fails

Expected results:
should complete installation

Additional info:
Comment 1 Yaniv Lavi 2013-08-12 07:17:21 EDT
*** Bug 992998 has been marked as a duplicate of this bug. ***
Comment 2 Yaniv Lavi 2013-08-19 05:57:26 EDT
*** Bug 998391 has been marked as a duplicate of this bug. ***
Comment 4 Barak Dagan 2013-10-07 04:20:52 EDT
Verified on is17.1 - clean installation passed.
Comment 5 Charlie 2013-11-27 19:49:01 EST
This bug is currently attached to errata RHEA-2013:15115. 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 8 errata-xmlrpc 2014-01-21 09:55:46 EST
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-2014-0035.html

Note You need to log in before you can comment on or make changes to this bug.