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

Bug 1816108

Summary: Make either the public network for all hosts or use same FQDN for both networks mandatory
Product: [oVirt] cockpit-ovirt Reporter: SATHEESARAN <sasundar>
Component: gluster-ansibleAssignee: Parth Dhanjal <dparth>
Status: CLOSED CURRENTRELEASE QA Contact: SATHEESARAN <sasundar>
Severity: high Docs Contact:
Priority: unspecified    
Version: 0.14.2CC: bugs, dparth, godas, rhs-bugs
Target Milestone: ovirt-4.4.0Flags: sasundar: ovirt-4.4?
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: cockpit-ovirt-0.14.5 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1816105 Environment:
Last Closed: 2020-05-20 20:02:20 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: 1816105    

Description SATHEESARAN 2020-03-23 11:21:35 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

--- Additional comment from SATHEESARAN on 2020-03-23 11:19:21 UTC ---
Comment 1 SATHEESARAN 2020-03-23 11:22:18 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 2 SATHEESARAN 2020-05-05 16:56:41 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 3 Sandro Bonazzola 2020-05-20 20:02:20 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.