Red Hat Bugzilla – Bug 1005851
Unable to bypass FQDN requirement for rhevm-setup
Last modified: 2013-12-27 10:26:31 EST
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:
Thanks in advance.
Added some document text could some one please check its accuracy?
Verified on RHEL 6.4 RHEVM3.2.5 SF22. rhevm-setup-3.2.5-0.48.el6ev.noarch
Host fully qualified domain name. Note: this name should be fully resolvable [sefi.tlv.redhat.com] : 10.35.0.153
10.35.0.153 is an IP address and not a FQDN. A FQDN is needed to be able to generate certificates correctly.
User input failed validation, do you still wish to use it? (yes|no): yes
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.