Bug 1816105 - Make either the public network for all hosts or use same FQDN for both networks mandatory
Summary: Make either the public network for all hosts or use same FQDN for both networ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: rhhi
Version: rhgs-3.5
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
: RHHI-V 1.8
Assignee: Parth Dhanjal
QA Contact: SATHEESARAN
URL:
Whiteboard:
Depends On: 1816108
Blocks: RHHI-V-1.8-Engineering-Inflight-BZs
TreeView+ depends on / blocked
 
Reported: 2020-03-23 11:11 UTC by SATHEESARAN
Modified: 2020-08-04 14:52 UTC (History)
2 users (show)

Fixed In Version: cockpit-ovirt-0.14.5
Doc Type: No Doc Update
Doc Text:
Clone Of:
: 1816108 (view as bug list)
Environment:
Last Closed: 2020-08-04 14:52:05 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2020:3314 0 None None None 2020-08-04 14:52:21 UTC

Description SATHEESARAN 2020-03-23 11:11:00 UTC
Description of problem:
------------------------
With the hyperconverged deployment from cockpit, the hosts tab provides option to provide storage network and public network FQDN. Also this page provides an option to make use of same FQDN for Storage and Public network.

If a user doesn't select the option to make use of same hostname for public and storage network, but decides to leave all the Public network FQDN empty, then the deployment proceeds to the next tab.

In the above case, user shouldn't be allowed to proceed to the next tab, until the user has chosen one of the following option:
1. Selected the checkbox - "use same hostname for public and storage network"
2. Populated all the text fields corresponding to the public network of all the hosts

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

How reproducible:
-----------------
always

Steps to Reproduce:
--------------------
1. Start the HC deployment from cockpit wizard
2. Do not select - "use same hostname for Storage and Public network"
3. Do not populate fields corresponding to Public network

Actual results:
---------------
Deployment proceeds to the next tab

Expected results:
-----------------
Deployment should fail proceeding to the next tab

Comment 1 SATHEESARAN 2020-03-23 11:19:21 UTC
Following changes are required as part of this bug

1. Either select "same hostname for Storage and Public network" or "Populate public network" for all hosts
-----------------------------------------------------------------------------------------------------------
if: (no public network provided) and (use same hostname for Storage&Public network not selected):
         Throw error: do not proceed the HC deployment
else:
    proceed to next tab

2. Error when not all the 3 public networks are pupulated
-----------------------------------------------------------
When not all the public networks are populated, then the error is thrown as
"Public Network missing. Either mention all or none."

It should be improvized as:
 "Public Network missing. Either mention all or check the option to use same hostname for storage and public network."

3. Correction with background text
-----------------------------------
Replace "Public Network" and "Storage Network" with
"Publicj Network FQDN" and "Storage Network FQDN" respectively

Comment 3 SATHEESARAN 2020-05-05 16:56:19 UTC
Tested with cockpit-ovirt-dashboard-0.14.5 with the following steps:

1. Start the HC deployment from the web console
2. On the hosts tab, provide only the 'Storage Network FQDN' but do not provide value for 'Public Network FQDN'
3. Proceed to the next tab.

Without 'Public network FQDN' one can't proceed to the next tab,
in the case when the user has only one network, the option 'Use same hostname for Storage and Gluster network',
helps in proceeding to the next tab

Comment 5 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


Note You need to log in before you can comment on or make changes to this bug.