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

Bug 948851

Summary:	document in rhevm-setup man page funcionality of answerfile and its syntax
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Jiri Belka <jbelka>
Component:	Documentation	Assignee:	Andrew Dahms <adahms>
Status:	CLOSED DUPLICATE	QA Contact:	ecs-bugs
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	3.4.0	CC:	acathrow, alonbl, gklein, iheim, Rhev-m-bugs, rlandman, yeylon
Target Milestone:	---
Target Release:	3.4.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-08-14 21:59:49 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 Jiri Belka 2013-04-05 13:39:59 UTC

Description of problem:

As mentioned in https://bugzilla.redhat.com/show_bug.cgi?id=838111#c10 answerfile syntax is pretty silly. By default it generates variables with no parameters, one can only guess which ones need to be modified to make rhevm-setup happy when reading answerfile.

So, document what should be put/changed into answerfile in man page. Especially how random password overrides any parameters for *PASS, and firewall stuff. Maybe some comments inside answerfile too?


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

How reproducible:
100%

Steps to Reproduce:
1. generate answerfile
2. check magic ball and guest what should be put in empty params
3.
  
Actual results:
some params cannot be empty but it is not obvious which ones

Expected results:
document how to edit answerfile in man page of rhevm-setup and state which variables are mandatory to be changed

Additional info:
not everybody has time to do try-test-cry until valid syntax is found

Comment 2 Alex Lourie 2013-08-22 21:11:05 UTC

Zac

1. AUTH_PASS is a password for the engine administrator user (admin@internal).
2. DB_HOST is a hostname for the DB server, in localinstall should be 'localhost'
3. DB_REMOTE_PASS and DB_LOCAL_PASS are the DB password for the admin user and are mutually exclusive. Use DB_REMOTE for remote installation and DB_LOCAL for local one.
4. OVERRIDE_FIREWALL is firewall option, either 'None' or 'iptables' on RHEL, and additional 'firewalld' on Fedora.

Don't hesitate to ask me other questions if you have them.

Comment 3 Zac Dover 2013-08-29 06:10:39 UTC

[root@localhost setup]# cat /var/lib/ovirt-engine/setup/answers/20130829013013-setup.conf
# action=setup
[environment:default]
OVESETUP_CORE/engineStop=none:None
OVESETUP_DIALOG/confirmSettings=bool:True
OVESETUP_DB/database=str:engine
OVESETUP_DB/fixDbViolations=none:None
OVESETUP_DB/secured=bool:False
OVESETUP_DB/host=str:localhost
OVESETUP_DB/user=str:engine
OVESETUP_DB/securedHostValidation=bool:False
OVESETUP_DB/password=str:8941vFvs
OVESETUP_DB/port=int:5432
OVESETUP_SYSTEM/nfsConfigEnabled=bool:True
OVESETUP_PKI/organization=str:localdomain
OVESETUP_CONFIG/isoDomainName=str:ISO_DOMAIN
OVESETUP_CONFIG/isoDomainMountPoint=str:/var/lib/exports/iso
OVESETUP_CONFIG/adminPassword=str:4xoFPMd/
OVESETUP_CONFIG/applicationMode=str:both
OVESETUP_CONFIG/firewallManager=str:iptables
OVESETUP_CONFIG/websocketProxyConfig=none:None
OVESETUP_CONFIG/fqdn=str:localhost.localdomain
OVESETUP_CONFIG/storageType=str:nfs
OVESETUP_PROVISIONING/postgresProvisioningEnabled=bool:True
OVESETUP_APACHE/configureRootRedirection=bool:True
OVESETUP_APACHE/configureSsl=bool:True
OSETUP_RPMDISTRO/requireRollback=bool:False
OSETUP_RPMDISTRO/enableUpgrade=bool:True
OVESETUP_AIO/configure=none:None
OVESETUP_AIO/storageDomainDir=none:None

Comment 4 Zac Dover 2013-08-30 00:26:38 UTC

Hi Itamar,

Can you show me how to get the man page for rhev so that I can create a patch documenting the syntax and function of the rhevm answerfile?

Thanks in advance.

Zac

Comment 5 Alon Bar-Lev 2013-08-30 07:15:38 UTC

(In reply to Zac Dover from comment #4)
> Hi Itamar,
> 
> Can you show me how to get the man page for rhev so that I can create a
> patch documenting the syntax and function of the rhevm answerfile?
> 
> Thanks in advance.
> 
> Zac

Hmm... We create the troff manually. If you provide plain text I can convert it to troff format.

There are quite a few generators, but I did not find anything that is good except of maybe xsltproc with man.xsl.

Comment 9 Andrew Dahms 2014-08-14 21:59:49 UTC

Because content on creating and using answer files during the engine-setup process has been included in the documentation, I am closing this bug for now. However, I will keep an eye on areas in which content on answer files and their parameters can be fleshed out and will raise bugs accordingly.

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