Description of problem: The host address used to add the host to the engine should resolve on the interface choose for the management bridge in order to correctly apply VLAN setting at engine eyes and so on. ovirt-ansible-hosted-engine setup role is correctly checking and enforcing this but, deploying from CLI, the user cannot really edit the address that it's going to be used as deploying from cockpit or directly using the role. On correctly configured environment this is fine but it can generate a bit of ambiguity where the FQDN resolves over a different interface and the user wants to use a different address (that resolves on the interface choose for the management network). Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: 1. deploy from CLI trying to edit the address used to add the host to the engine 2. 3. Actual results: deploying for CLI it always try the FQDN Expected results: it should let the user review and eventually customize that value Additional info: Deploying from cockpit or directly from the role customizing that value is already possible.
This is a duplicate of bug 1188675. Now fixed, after 4 years :-) Better late than never :-))
I think that we have fixed and reopened it more then once in the meantime.
[ INFO ] Stage: Setup validation Please provide the hostname of this host on the management network [alma03.qa.lab.tlv.redhat.com]: alma03.qa.lab.tlv.redhat.com Its now possible to edit FQDN of ha-host via CLI. Works for me on these components: ovirt-hosted-engine-setup-2.3.7-1.el7ev.noarch ovirt-hosted-engine-ha-2.3.1-1.el7ev.noarch rhvm-appliance-4.3-20190328.1.el7.x86_64 Linux 3.10.0-957.10.1.el7.x86_64 #1 SMP Thu Feb 7 07:12:53 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux Red Hat Enterprise Linux Server release 7.6 (Maipo) Tested on RHEL host. Moving to verified.
This bugzilla is included in oVirt 4.3.3 release, published on April 16th 2019. Since the problem described in this bug report should be resolved in oVirt 4.3.3 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.