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

Bug 1573070

Summary:	Documentation required - engine answers file
Product:	[oVirt] ovirt-hosted-engine-setup	Reporter:	Sam McLeod <mailinglists>
Component:	Documentation	Assignee:	Ido Rosenzwig <irosenzw>
Status:	CLOSED DUPLICATE	QA Contact:	meital avital <mavital>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	2.2.16	CC:	bugs
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-04-30 10:42:41 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Docs	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Sam McLeod 2018-04-30 06:05:49 UTC

Description of problem:

It appears there is no documentation for the ovirt-engine --deploy `answers.conf` file.

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

ovirt-hosted-engine-setup-2.2.16-1.el7.centos.noarch

How reproducible:

Every time

Steps to Reproduce:
1. man answers.conf
2. Check ovirt website documentation
3. Search using google or ddg for ovirt answers.conf documentation

Actual results:

Doesn't appear to be any documentation or a list of options

Expected results:

Documentation and a list of available options.

Additional information:

Real world example:

I wanted to set the default engine VM and engine admin password during install.

After a bit of googling I found [someones gist](https://github.com/HighOps/ovirt_hosted_engine_install/blob/master/templates/ovirt-answer.conf), in which I spotted:

* `OVEHOSTED_VM/cloudinitRootPwd`
* `OVEHOSTED_ENGINE/interactiveAdminPassword`

These worked for me, but I don't know if I _should_ be using them or if for example they are going to be deprecated in the future.

Comment 1 Ido Rosenzwig 2018-04-30 10:42:41 UTC


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