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

Bug 1166077

Summary:	[ENGINE-SETUP] - Once dwh & reports are not installed in the 1st install, these options are not presented in the 2nd time
Product:	[Retired] oVirt	Reporter:	Shirly Radco <sradco>
Component:	ovirt-engine-dwh	Assignee:	Shirly Radco <sradco>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Petr Kubica <pkubica>
Severity:	low	Docs Contact:
Priority:	low
Version:	3.3	CC:	alonbl, bazulay, bdagan, bugs, dfediuck, didi, ecohen, gklein, iheim, istein, juwu, lsurette, movciari, nbarcet, pstehlik, rbalakri, Rhev-m-bugs, sbonazzo, sradco, tdosek, yeylon, ylavi
Target Milestone:	---
Target Release:	3.6.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	integration
Fixed In Version:		Doc Type:	Known Issue
Doc Text:	Cause: If the user installed dwh and reports rpms but when he run engine-setup chose not to setup them, the setup will not ask again if he wants to install them on the next run. Consequence: The user might not know how to install the dwh and reports at this point Workaround (if any): A new flag was added to engine-setup --reconfigure-optional-components. If this flag was added all components that are defined as re-configurable will be asked again during the setup. Result: A simple way for the user to be asked again what components he wishes to setup.	Story Points:	---
Clone Of:	1072360
Clones:	1166078 1277061 (view as bug list)		Environment:
Last Closed:	2015-11-04 13:46:50 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:	1072360
Bug Blocks:	1166078, 1277061

Comment 3 Julie 2014-11-24 07:47:57 UTC

Hi Didi and Shirly,
   Thanks for chipping in your thoughts. My understanding was this is a known issues for 3.5 and therefore asking for 3.5 release notes. There wasn't a 3.5 engineering bug, so asking in this 3.6 bug. Sorry for the confusion. If you think it's okay to let the main 3.5 documentation cover this and it doesn't need to be called out again in release notes, we can leave it as is.

Many thanks,
Julie

Comment 6 Petr Kubica 2015-06-19 12:26:45 UTC

added new option to engine-setup

engine-setup --help
...
    --reconfigure-optional-components
        Ask again about components that were disabled in previous run.
...

Verified with:
ENGINE: ovirt-engine-3.6.0-0.0.master.20150617172413.git0933d9a.el6.noarch
DWH: ovirt-engine-dwh-3.6.0-0.0.master.20150617151108.20150617150804.gitfccbb7a.el6.noarch

Comment 7 Yedidyah Bar David 2015-11-02 08:01:38 UTC

Julie, please take care of this bug - perhaps clone it as a doc bug or whatever.

IMO this should be documented in the main docs, not (only?) in release notes.

It's up to you where exactly.

The new option '--reconfigure-optional-components' for engine-setup currently applies to:
- DWH
- Reports
- Docker Cinder container (bug 1195131)
- Docker Glance container (bug 1195127)

I didn't personally try the last two.

Note that this option cannot be used to disable/remove a component, only to enable if not already done.

Comment 8 Julie 2015-11-02 08:49:43 UTC

Hey Didi,
   Thanks for bringing this to my attention. Yes, I agree this needs to be added to the main docs suite. 

Kind regards,
Julie

Comment 9 Sandro Bonazzola 2015-11-04 13:46:50 UTC

oVirt 3.6.0 has been released on November 4th, 2015 and should fix this issue.
If problems still persist, please open a new BZ and reference this one.