Bug 1026089

Summary:	Setup - When installing report without DWH installed it doesn't check DWH status.
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Yaniv Lavi <ylavi>
Component:	ovirt-engine-reports	Assignee:	Alex Lourie <alourie>
Status:	CLOSED UPSTREAM	QA Contact:	Barak Dagan <bdagan>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	3.3.0	CC:	acathrow, alourie, iheim, pstehlik, Rhev-m-bugs, srevivo, yeylon, ylavi
Target Milestone:	---	Keywords:	Triaged
Target Release:	3.3.0
Hardware:	x86_64
OS:	Linux
Whiteboard:	integration
Fixed In Version:	IS23 - rhevm-reports-3.3.0-20.el6ev.noarch.rpm	Doc Type:	Bug Fix
Doc Text:	This new implementation requires the Manager and DWH to be run and set up correctly before the reports package can be set up. If the settings for the Manager or DWH are not found, the reports setup will exit with a corresponding message. The database configuration is now defined in a spec file.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-11-14 13:19:05 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:
Bug Blocks:	1032811

Description Yaniv Lavi 2013-11-03 15:28:53 UTC

Description of problem:
When installing report without DWH installed it doesn't check DWH status. This causes setup to fail and no message instructing the user to install dwh first.

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

How reproducible:
Always

Steps to Reproduce:
1. install rhevm-report rpm
2. install engine
3. run rhevm-reports setup

Actual results:
stops with exception 

Expected results:
should dispaly message telling use to install dwh first

Additional info:

Comment 1 Alex Lourie 2013-11-11 11:14:56 UTC

Please reproduce with last build.

Comment 3 Shai Revivo 2013-11-14 13:19:05 UTC

his bug was fixed and is slated to be in the upcoming version. As we are focusing our testing at this phase on severe bugs, this bug was closed without going through its verification step

Comment 4 Charlie 2013-11-28 00:49:06 UTC

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.