Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1688794

Summary: Need an option to get IP version type used for FQDNs from user
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, sabose
Target Milestone: ovirt-4.4.0Flags: sasundar: ovirt-4.4?
godas: devel_ack+
sasundar: testing_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:
: 1688798 (view as bug list) Environment:
Last Closed: 2020-05-20 20:04:23 UTC Type: Bug
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: 1688798    

Description SATHEESARAN 2019-03-14 13:16:17 UTC 
Description of problem:
-----------------------
Need an option in HC cockpit deployment wizard, that would help in identifying the IPV6 FQDN, if provided by the user

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

How reproducible:
-----------------
Not applicable

Steps to Reproduce:
-------------------
Not applicable

Actual results:
---------------
No option available to identify whether the given FQDN belongs to IPV6 or IPV4

Expected results:
-----------------
Additional input expected from the user to provide if its a IPV6
Comment 2 SATHEESARAN 2020-03-30 13:44:54 UTC 
Tested with cockpit-ovirt-dashboard-0.14.3

Start the HC deployment using cockpit wizard.
Hosts tab has an checkbox to select if its IPV6 hosts

The same is available for 3 node host deployment and also
for single node deployment
Comment 3 Sandro Bonazzola 2020-05-20 20:04:23 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.