Description of problem: hosted-engine --deploy command led me to choose the FQDN for the engine, stating this shouldn't be of an existent machine in the system. I made up a name and got an error as follows: -------------------------------------------------------- Please provide the FQDN for the engine you would like to use. This needs to match the FQDN that you will use for the engine installation within the VM. Note: This will be the FQDN of the VM you are now going to create, it should not point to the base host or to any other existing machine. Engine FQDN: aaaa [WARNING] Host name aaaa has no domain suffix [ ERROR ] Host name is not valid: aaaa did not resolve into an IP address -------------------------------------------------------------- Version-Release number of selected component (if applicable): ovirt-hosted-engine-setup-1.2.0-0.1.master.20140908073913.git480e272.fc20.noarch Expected results: As a user I'd expect a suggestion on how this error should be solve, or better yet, a guidance when asking for the FQDN to do so with a name in /etc/hosts. If this is done, it will not be complete without an instruction to give a fake IP at first and not forget to change it to the assigned IP after the deployment is done. Document URL: Section Number and Name: Describe the issue: Suggestions for improvement: Additional information: Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Well.. fqdn means fully qualified domain name. "aaa" is not that at all.. /etc/hosts is just a workaround you use when testing. The name should be resolvable using standard DNS resolver in real deployment. That can be probably added there.
Not a bug, customer's IT have to provide reserved FQDN and IP address pinned to predefined MAC, hence engine's IP won't change on DHCP renew, even if not reserved, DDNS have to be configured properly by IT, either the way, IT should provide stable infrastructure as a pre-requirement. As mentioned in comment #1, "aaaa" is not FQDN in any way, as a result it failed to resolve in to IP through customers DNS. If you're working with /etc/hosts file locally, you should edit it accordingly to IP/name on hosts and engine's VM, otherwise they won't resolve name to IP and of course you have to provide FQDN in form of "somehost.example.com". Hosted engine deployment is well described in user guide, hence should be followed accordingly bu a customer. Please review step 5 at https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Virtualization/3.3/html/Installation_Guide/Configuring_the_Self-Hosted_Engine.html "Provide the FQDN for HostedEngine-VM; this procedure uses the FQDN HostedEngine-VM.example.com."