Bug 1690820

Summary: Day 2: Host1 value in volume tab should populate FQDN name
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: bipin <bshetty>
Component: rhhiAssignee: Parth Dhanjal <dparth>
Status: CLOSED NOTABUG QA Contact: SATHEESARAN <sasundar>
Severity: medium Docs Contact:
Priority: medium    
Version: rhhiv-1.6CC: bugs, godas, guillaume.pavese, rhs-bugs, sabose, sasundar
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Known Issue
Doc Text:
When you create a new volume using the Cockpit UI using the "Create Volume" button, the value for hosts is populated from gluster peer list, and the first host is an IP address instead of an FQDN. As part of volume creation, this value is passed to an FQDN validation process, which fails with an IP address. To work around this issue, edit the generated variable file and manually insert the FQDN instead of the IP address.
 Story Points: ---
Clone Of: 1690807 Environment:
Last Closed: 2020-03-02 07:26:58 UTC Type: ---
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: 1690807    
Bug Blocks: 1683647    

Description bipin 2019-03-20 10:01:10 UTC 
+++ This bug was initially created as a clone of Bug #1690807 +++

Description of problem:
======================
The Host1 value in Volume tab always displays IP during the Day 2 volume creation. This affects the flow when the check to validate proper FQDN pitches in ansible. 

Version-Release number of selected component (if applicable):
============================================
cockpit-ovirt-dashboard-0.12.5-1.el7ev.noarch
ansible-2.7.8-1.el7ae.noarch
gluster-ansible-cluster-1.0-1.el7rhgs.noarch
gluster-ansible-roles-1.0.4-4.el7rhgs.noarch

How reproducible:
================
Always

Steps to Reproduce:
==================
1.Start Day 2 volume creation using the cockpit UI
2.First tab (Volume) we can see the host1 displaying the IP not the FQDN


Actual results:
==============
The check to validate proper FQDN fails since it has the IP listed

Expected results:
================
The check should pass provided the FQDN is used for the Host1

Additional info:
===============
There is a workaround where we can edit the inventory file and replace the IP with the FQDN name

--- Additional comment from bipin on 2019-03-20 09:52:47 UTC ---

2019-03-20 13:10:28,752 p=17809 u=root |  TASK [gluster.features/roles/gluster_hci : Check if valid FQDN is provided] ****
2019-03-20 13:10:29,208 p=17809 u=root |  failed: [10.70.45.29 -> localhost] (item=10.70.45.29) => {"changed": true, "cmd": ["dig", "10.70.45.29", "+short"], "delta": "0:00:00.214760", "end": "2019-03-20 13:10:2
9.176274", "failed_when_result": true, "item": "10.70.45.29", "rc": 0, "start": "2019-03-20 13:10:28.961514", "stderr": "", "stderr_lines": [], "stdout": "", "stdout_lines": []}
2019-03-20 13:10:29,449 p=17809 u=root |  changed: [10.70.45.29 -> localhost] => (item=rhsqa-grafton8.lab.eng.blr.redhat.com)
2019-03-20 13:10:29,695 p=17809 u=root |  changed: [10.70.45.29 -> localhost] => (item=rhsqa-grafton9.lab.eng.blr.redhat.com)
2019-03-20 13:10:29,697 p=17809 u=root |  NO MORE HOSTS LEFT *************************************************************
2019-03-20 13:10:29,707 p=17809 u=root |        to retry, use: --limit @/usr/share/cockpit/ovirt-dashboard/ansible/hc_wizard.retry
Comment 3 SATHEESARAN 2019-03-26 10:55:09 UTC 
Marking this bug as the known_issue for RHHI-V 1.6.

The first host always listed with IP, eventhough FQDN was used for deployment.
User need to edit generated vars file to have the FQDN instead of IP, else
the FQDN_validation will fail with IPs
Comment 5 Sahina Bose 2019-03-29 13:43:41 UTC 
Made some changes to clarify the cause.