Description of problem:
Can't use FQDN of the host for naming it during HE deployment over IPV6 over oVirt Node. 

[ INFO  ] Stage: Setup validation
          Please provide the hostname of this host on the management network [example]: 
[ ERROR ] Host name is not valid: example resolves to <ipv6 masked> <ipv4 masked> and not all of them can be mapped to non loopback devices on this host





# hosted-engine --deploy --6
[ INFO  ] Stage: Initializing
[ INFO  ] Stage: Environment setup
          During customization use CTRL-D to abort.
          Continuing will configure this host for serving as hypervisor and will create a local VM with a running engine.
          The locally running engine will be used to configure a new storage domain and create a VM there.
          At the end the disk of the local VM will be moved to the shared storage.
          Are you sure you want to continue? (Yes, No)[Yes]: 
          It has been detected that this program is executed through an SSH connection without using tmux.
          Continuing with the installation may lead to broken installation if the network connection fails.
          It is highly recommended to abort the installation and run it inside a tmux session using command "tmux".
          Do you want to continue anyway? (Yes, No)[No]: yes
          Configuration files: 
          Log file: /var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-20211011103329-q3ah9t.log
          Version: otopi-1.9.5 (otopi-1.9.5-1.el8)
[ INFO  ] DNF Updating Subscription Management repositories.
[ INFO  ] DNF Unable to read consumer identity
[ INFO  ] DNF 
         This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register.
         
[ INFO  ] Stage: Environment packages setup
[ INFO  ] DNF Updating Subscription Management repositories.
[ INFO  ] DNF Unable to read consumer identity
[ INFO  ] DNF 
         This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register.
         
[ INFO  ] Stage: Programs detection
[ INFO  ] Stage: Environment setup (late)
[ INFO  ] Stage: Environment customization
         
          --== STORAGE CONFIGURATION ==--
         
         
          --== HOST NETWORK CONFIGURATION ==--
         
          Please indicate the gateway IP address []: <ipv6 masked>
[ INFO  ] Checking available network interfaces:
[ INFO  ] TASK [ovirt.ovirt.hosted_engine_setup : Execute just a specific set of steps]
[ INFO  ] ok: [localhost]
[ INFO  ] TASK [ovirt.ovirt.hosted_engine_setup : Force facts gathering]
[ INFO  ] ok: [localhost]
[ INFO  ] TASK [ovirt.ovirt.hosted_engine_setup : Detecting interface on existing management bridge]
[ INFO  ] TASK [ovirt.ovirt.hosted_engine_setup : Set variable for supported bond modes]
[ INFO  ] ok: [localhost]
[ INFO  ] TASK [ovirt.ovirt.hosted_engine_setup : Get all active network interfaces]
[ INFO  ] ok: [localhost]
[ INFO  ] TASK [ovirt.ovirt.hosted_engine_setup : Filter bonds with bad naming]
[ INFO  ] ok: [localhost]
[ INFO  ] TASK [ovirt.ovirt.hosted_engine_setup : Generate output list]
[ INFO  ] ok: [localhost]
[ INFO  ] TASK [ovirt.ovirt.hosted_engine_setup : Collect interface types]
[ INFO  ] changed: [localhost]
[ INFO  ] TASK [ovirt.ovirt.hosted_engine_setup : Check for Team devices]
[ INFO  ] TASK [ovirt.ovirt.hosted_engine_setup : Get list of Team devices]
[ INFO  ] ok: [localhost]
[ INFO  ] TASK [ovirt.ovirt.hosted_engine_setup : Collect Team devices]
[ INFO  ] ok: [localhost]
[ INFO  ] TASK [ovirt.ovirt.hosted_engine_setup : Filter team devices]
[ INFO  ] ok: [localhost]
[ INFO  ] TASK [ovirt.ovirt.hosted_engine_setup : Fail if only team devices are available]
[ INFO  ] skipping: [localhost]
[ INFO  ] TASK [ovirt.ovirt.hosted_engine_setup : Search VLAN devices]
[ INFO  ] TASK [ovirt.ovirt.hosted_engine_setup : Check for base interface of VLAN devices]
[ INFO  ] TASK [ovirt.ovirt.hosted_engine_setup : Get base interface types of VLAN devices]
[ INFO  ] TASK [ovirt.ovirt.hosted_engine_setup : Check for bond as base type of VLAN device]
[ INFO  ] TASK [ovirt.ovirt.hosted_engine_setup : Check if bond base interface of VLAN device is in supported mode]
[ INFO  ] TASK [ovirt.ovirt.hosted_engine_setup : Collect VLAN devices with bad bond mode base interfaces]
[ INFO  ] TASK [ovirt.ovirt.hosted_engine_setup : Generate invalid VLANs list]
[ INFO  ] ok: [localhost]
[ INFO  ] TASK [ovirt.ovirt.hosted_engine_setup : Create list of unsupported network devices]
[ INFO  ] ok: [localhost]
[ INFO  ] TASK [ovirt.ovirt.hosted_engine_setup : Collect VLAN devices naming convention pattern]
[ INFO  ] TASK [ovirt.ovirt.hosted_engine_setup : Check VLAN devices with bad naming]
[ INFO  ] TASK [ovirt.ovirt.hosted_engine_setup : Collect VLAN devices with invalid naming convention]
[ INFO  ] ok: [localhost]
[ INFO  ] TASK [ovirt.ovirt.hosted_engine_setup : Filter VLAN devices with invalid naming convention]
[ INFO  ] ok: [localhost]
[ INFO  ] TASK [ovirt.ovirt.hosted_engine_setup : Fail if only VLAN devices with invalid naming convention are available]
[ INFO  ] skipping: [localhost]
[ INFO  ] TASK [ovirt.ovirt.hosted_engine_setup : Check for base interface of VLAN devices]
[ INFO  ] TASK [ovirt.ovirt.hosted_engine_setup : Get base interface types of VLAN devices]
[ INFO  ] TASK [ovirt.ovirt.hosted_engine_setup : Check for bond as base type of VLAN device]
[ INFO  ] TASK [ovirt.ovirt.hosted_engine_setup : Check if bond base interface of VLAN device is in supported mode]
[ INFO  ] TASK [ovirt.ovirt.hosted_engine_setup : Check VLAN devices with bad bond mode base interfaces]
[ INFO  ] TASK [ovirt.ovirt.hosted_engine_setup : Collect unsupported VLAN bonds]
[ INFO  ] ok: [localhost]
[ INFO  ] TASK [ovirt.ovirt.hosted_engine_setup : Filter VLAN devices with invalid bond mode base interface]
[ INFO  ] ok: [localhost]
[ INFO  ] TASK [ovirt.ovirt.hosted_engine_setup : Fail if only VLAN devices with bad bond mode are available]
[ INFO  ] skipping: [localhost]
[ INFO  ] TASK [ovirt.ovirt.hosted_engine_setup : Generate list of all unsupported VLAN devices]
[ INFO  ] ok: [localhost]
[ INFO  ] TASK [ovirt.ovirt.hosted_engine_setup : Generate list of all unsupported network devices]
[ INFO  ] ok: [localhost]
[ INFO  ] TASK [ovirt.ovirt.hosted_engine_setup : Filter unsupported interface types]
[ INFO  ] ok: [localhost]
[ INFO  ] TASK [ovirt.ovirt.hosted_engine_setup : Failed if only unsupported devices are available]
[ INFO  ] skipping: [localhost]
[ INFO  ] TASK [ovirt.ovirt.hosted_engine_setup : Validate selected bridge interface if management bridge does not exist]
[ INFO  ] skipping: [localhost]
          Please indicate a nic to set ovirtmgmt bridge on (enp3s0f0) [enp3s0f0]: 
          Please specify which way the network connectivity should be checked (ping, dns, tcp, none) [dns]: 
         
          --== VM CONFIGURATION ==--
         
         
          Please enter the name of the data center where you want to deploy this hosted-engine host.
          Data center [Default]: 
         
          Please enter the name of the cluster where you want to deploy this hosted-engine host.
          Cluster [Default]: 
         
          If you want to deploy with a custom engine appliance image, please specify the path to the OVA archive you would like to use.
          Entering no value will use the image from the rhvm-appliance rpm, installing it if needed.
          Appliance image path []: /usr/share/ovirt-engine-appliance/rhvm-appliance-4.4-20210827.0.el8ev.ova
[ INFO  ] Checking OVF archive content (could take a few minutes depending on archive size)
[ INFO  ] Checking OVF XML content (could take a few minutes depending on archive size)
          Please specify the number of virtual CPUs for the VM. The default is the appliance OVF value [4]: 
          Please specify the memory size of the VM in MB. The default is the appliance OVF value [16384]: 
[ INFO  ] Detecting host timezone.
          Please provide the FQDN you would like to use for the engine.
          Note: This will be the FQDN of the engine VM you are now going to launch,
          it should not point to the base host or to any other existing machine.
          Engine VM FQDN:  []: <engine fqdn masked>
          Please provide the domain name you would like to use for the engine appliance.
          Engine VM domain [<masked>]: 
          Enter root password that will be used for the engine appliance: 
          Confirm appliance root password: 
         
          You may provide an SSH public key, that will be added by the deployment script to the authorized_keys file of the root user in the engine appliance.
          This should allow you passwordless login to the engine machine after deployment.
          If you provide no key, authorized_keys will not be touched.
          SSH public key []: 
[WARNING] Skipping appliance root ssh public key
          Do you want to enable ssh access for the root user? (yes, no, without-password) [yes]: 
          Do you want to apply a default OpenSCAP security profile? (Yes, No) [No]: 
          Do you want to enable FIPS? (Yes, No) [No]: 
          Please specify a unicast MAC address for the VM, or accept a randomly generated default [00:16:3e:24:58:e9]: 00:1a:4a:25:01:05
          How should the engine VM network be configured? (DHCP, Static)[DHCP]: Static
          Please enter the IP address to be used for the engine VM []: 2620:52:0:235c:21a:4aff:fe25:105
[ INFO  ] The engine VM will be configured to use 2620:52:0:235c:21a:4aff:fe25:105/64
          Please provide a comma-separated list (max 3) of IP addresses of domain name servers for the engine VM
          Engine VM DNS (leave it empty to skip) []: 2620:52:0:2e00:5054:ff:fe12:1070
         
          Add lines for the appliance itself and for this host to /etc/hosts on the engine VM?
          Note: ensuring that this host could resolve the engine VM hostname is still up to you.
          Add lines to /etc/hosts? (Yes, No)[Yes]: 
         
          --== HOSTED ENGINE CONFIGURATION ==--
         
          Please provide the name of the SMTP server through which we will send notifications [localhost]: 
          Please provide the TCP port number of the SMTP server [25]: 
          Please provide the email address from which notifications will be sent [root@localhost]: 
          Please provide a comma-separated list of email addresses which will get notifications [root@localhost]: 
          Enter engine admin password: 
          Confirm engine admin password: 
[ INFO  ] Stage: Setup validation
          Please provide the hostname of this host on the management network [example.domain.com]: 
[ ERROR ] Host name is not valid: example.domain.com resolves to <iv6 address masked> <ipv4 masked> and not all of them can be mapped to non loopback devices on this host
          Please provide the hostname of this host on the management network [example.domain.com]: 

Version-Release number of selected component (if applicable):
Linux 4.18.0-305.17.1.el8_4.x86_64 #1 SMP Mon Aug 30 07:26:31 EDT 2021 x86_64 x86_64 x86_64 GNU/Linux
Red Hat Enterprise Linux release 8.4
rhvm-appliance-4.4-20210827.0.el8ev.x86_64
ansible-2.9.23-1.el8ae.noarch
ovirt-ansible-collection-1.6.2-1.el8ev.noarch


How reproducible:
100%

Steps to Reproduce:
1.Reprovision host to clean RHVH 
2.Install appliance on RHVH
3.Configure RHVH to use IPV6
4.Deploy HE using "hosted-engine --deploy --6"
5.Use DNS for "Please specify which way the network connectivity should be checked (ping, dns, tcp, none) [dns]:"

Actual results:
Deployment fails with "[ ERROR ] Host name is not valid: example.domain.com resolves to <ipv6 address masked> <ipv4 masked> and not all of them can be mapped to non loopback devices on this host"

Expected results:
Deployment should succeed.

Additional info:
My thoughts about this is that DNS returns both IPV6 and IPv4 addresses and deployment can't configure both.