Bug 928386

Summary:	can't run --no-mem-check option while using --answer-file when running engine-setup
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Eyal Edri <eedri>
Component:	ovirt-engine-setup	Assignee:	Sandro Bonazzola <sbonazzo>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Ilanit Stein <istein>
Severity:	high	Docs Contact:
Priority:	high
Version:	3.2.0	CC:	acathrow, bazulay, dyasny, iheim, mgoldboi, Rhev-m-bugs, sbonazzo, sgrinber, ykaul
Target Milestone:	---	Keywords:	TestBlocker
Target Release:	3.2.0
Hardware:	x86_64
OS:	Linux
Whiteboard:	integration
Fixed In Version:	sf13	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		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 Eyal Edri 2013-03-27 14:37:29 UTC

Description of problem:

Executing command --> 'rhevm-setup --no-mem-check --answer-file=answer_file'
Usage: rhevm-setup [options]

Options:
  -h, --help            show this help message and exit
 ......

Error: The --answer-file flag is mutually exclusive to all other command line options
Please check log file /var/log/ovirt-engine/engine-setup_2013_03_27_16_16_59.log for more information


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


How reproducible:
always

Steps to Reproduce:
1.run engine-setup --no-mem-check --answer=ans_file
2.
3.
  
Actual results:
setup fails

Expected results:
either allow this option to run with answer file or enable this option in the answer file

Additional info:

Comment 1 Simon Grinberg 2013-03-28 13:31:36 UTC

The fix should be to convert the abort to warning

- on interactive mode, stop, warn and ask if to abort 
- on answer file mode don't stop, issue the warning in the log. The assumption here is that users of the answer file are aware of the requirements and had to read the manual to use this option.

Comment 2 Sandro Bonazzola 2013-04-02 07:15:11 UTC

patch 13409 merged upstream master: http://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=commit;h=014ae9a67bacc339e89209672fb5a26ca2c5f853

Comment 3 Ilanit Stein 2013-04-07 14:13:31 UTC

On sf-13 option --no-mem-check removed. Don't we need this option?

Comment 4 Sandro Bonazzola 2013-04-08 07:14:32 UTC

Hi Ilanit, no the option is not needed anymore. --no-mem-check were used for avoiding an abort in engine-setup if the installed RAM was less than the minimum required. Now we just warn without aborting the setup, so it's not needed anymore.

Comment 5 Ilanit Stein 2013-04-08 10:23:22 UTC

I understand. Moved to verified.

Comment 6 Itamar Heim 2013-06-11 09:50:48 UTC

3.2 has been released

Comment 7 Itamar Heim 2013-06-11 09:51:20 UTC

3.2 has been released

Comment 8 Itamar Heim 2013-06-11 09:58:22 UTC

3.2 has been released