Bug 1186742

Summary:	Cannot full automated setup additional host
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Amador Pahim <asegundo>
Component:	ovirt-hosted-engine-setup	Assignee:	Sandro Bonazzola <sbonazzo>
Status:	CLOSED DUPLICATE	QA Contact:	Artyom <alukiano>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3.4.4	CC:	didi, ecohen, gklein, iheim, istein, lsurette, lveyde, oourfali, stirabos
Target Milestone:	---
Target Release:	3.6.0
Hardware:	All
OS:	Linux
Whiteboard:	integration
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-02-03 13:29:45 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:

Description Amador Pahim 2015-01-28 13:06:43 UTC

Description of problem:

Adding an additional host to hosted-engine setup, I managed to skip the questions bellow using the answers.conf file:

  "Please specify the Host ID [Must be integer, default: 2]:"

Skipped with: OVEHOSTED_STORAGE/hostID=int:2

  "The specified storage location already contains a data domain. Is this an additional host setup (Yes, No)[Yes]?"

Skipped with OVEHOSTED_CORE/isAdditionalHost:bool:True


But a last question is avoiding the fully automated setup:

  [ INFO  ] Stage: Closing up
            To continue make a selection from the options below:
            (1) Continue setup - engine installation is complete
            (2) Power off and restart the VM
            (3) Abort setup
         
            (1, 2, 3)[1]: 


Please provide an option to be used in answers.conf file that can skip this question as well.


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

ovirt-hosted-engine-setup-1.1.5-1.el6ev.noarch

Comment 1 Sandro Bonazzola 2015-02-03 13:29:45 UTC

Thanks for the report, a RFE for allowing fully automated deployment has been already filled as bug #1101297.

*** This bug has been marked as a duplicate of bug 1101297 ***