Bug 1816090

Summary: Direct usage of IPv6 addresses shouldn't be allowed
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: SATHEESARAN <sasundar>
Component: rhhiAssignee: Parth Dhanjal <dparth>
Status: CLOSED ERRATA QA Contact: SATHEESARAN <sasundar>
Severity: high Docs Contact:
Priority: unspecified    
Version: rhgs-3.5CC: godas, rhs-bugs
Target Milestone: ---   
Target Release: RHHI-V 1.8   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: cockpit-ovirt-0.14.5 Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of:
: 1816095 (view as bug list) Environment:
Last Closed: 2020-08-04 14:52:05 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1816095    
Bug Blocks: 1779977    

Description SATHEESARAN 2020-03-23 10:38:38 UTC
Description of problem:
-----------------------
Usage of IPV6 addresses directly on the hosts tab shouldn't be allowed as the backup-volfile-servers mount option will not work with multiple IPV6 addresses directly


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


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

Steps to Reproduce:
--------------------
1. Populate hosts tab with IPv6 address directly

Actual results:
----------------
Usage of IPV6 address is not called as error in the UI


Expected results:
------------------
On sensing that the input is IPv6, the deployment should prompt the error and should not allow the users to proceed

Comment 2 SATHEESARAN 2020-05-05 16:52:04 UTC
Tested with cockpit-ovirt-dashboard-0.14.5 with the following steps:

1. Start the HC deployment from the web console
2. Use the option to enable IPV6
3. Provide the direct IPV6 addresses for the hosts.

Invalid FQDN error message is thrown in the above case

Comment 4 errata-xmlrpc 2020-08-04 14:52:05 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (RHHI for Virtualization 1.8 bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2020:3314