Bug 1688271

Summary: Additional hosts with IPV6 addresses doesn't qualify for valid addresses
Product: [oVirt] cockpit-ovirt Reporter: SATHEESARAN <sasundar>
Component: gluster-ansibleAssignee: Gobinda Das <godas>
Status: CLOSED CURRENTRELEASE QA Contact: SATHEESARAN <sasundar>
Severity: high Docs Contact:
Priority: high    
Version: 0.12.4CC: bugs, rhs-bugs, sabose
Target Milestone: ovirt-4.4.0Flags: sasundar: ovirt-4.4?
godas: devel_ack+
Target Release: 0.14.1   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: cockpit-ovirt-0.14.1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1688269 Environment:
Last Closed: 2020-08-05 06:09:52 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Gluster RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1688269, 1721383    

Description SATHEESARAN 2019-03-13 12:26:27 UTC 
Description of problem:
-----------------------
Cockpit wizard for RHHI-V deployment has FQDN tab, where customer can provide the FQDN of 2nd and 3rd host, which would be automatically added to the RHHI cluster.

When IPV6 FQDNs are provided, the hostnames are not considered valid

Version-Release number of selected component (if applicable):
-------------------------------------------------------------
cockpit-ovirt-dashboard-0.12.4

How reproducible:
-----------------
Always

Steps to Reproduce:
--------------------
1. Provide IPV6 FQDNs for additional hosts

Actual results:
---------------
IPV6 FQDNs are not accepted

Expected results:
----------------
IPV6 FQDNs should be considered legitimate
Comment 2 SATHEESARAN 2020-05-28 02:28:19 UTC 
Verified with cockpit-ovirt-dashboard-0.14.6-1.el8

Additional hosts validation works good for IPV6 addresses.

1. Directly using the IPv6 is not considered as valid IP addresses
2. Ping6 test is done for such IPv6 FQDNs
Comment 3 Sandro Bonazzola 2020-08-05 06:09:52 UTC 
This bugzilla is included in oVirt 4.4.0 release, published on May 20th 2020.

Since the problem described in this bug report should be
resolved in oVirt 4.4.0 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.