+++ This bug is a RHEV-M zstream clone. The original bug is: +++ +++ https://bugzilla.redhat.com/show_bug.cgi?id=916107. +++ +++ Requested by "idith" +++ ====================================================================== ---------------------------------------------------------------------- Following comment by obasan on February 27 at 10:20:16, 2013 Description of problem: When the setup validates a parameter in the answer file in engine-setup it throws an "error reading parameter" error. this is very confusing. since reading was successful. validation is the failure. Version-Release number of selected component (if applicable): How reproducible: always Steps to Reproduce: 1.run the engine setup with the --answer-file parameter and supply a parameter that will fail in validation. for example wrong fqdn Actual results: "Error reading parameter" Expected results: should output "failed validating parameter" ---------------------------------------------------------------------- Following comment by alourie on September 29 at 13:57:21, 2013 Andrew This is not relevant for 3.3, only 3.2.z What should I do with this bug? ---------------------------------------------------------------------- Following comment by italkohe on October 10 at 11:53:31, 2013 Suggest z-stream flag per Alex's request. ---------------------------------------------------------------------- Following comment by alourie on October 10 at 12:39:13, 2013 Moving to ON_QA to verify that it is not relevant for 3.3 Then it can be cloned to 3.2.z
This bug is currently attached to errata RHBA-2013:16431. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag. Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information: * Cause: What actions or circumstances cause this bug to present. * Consequence: What happens when the bug presents. * Fix: What was done to fix the bug. * Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore') Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug. For further details on the Cause, Consequence, Fix, Result format please refer to: https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes Thanks in advance.
Verifired on RHEL 6.4, RHEVM 3.2.5 SF22 rhevm-setup-3.2.5-0.48.el6ev.noarch
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2013-1831.html