Bug 1690807 - Day 2: Host1 value in volume tab should populate FQDN name
Summary: Day 2: Host1 value in volume tab should populate FQDN name
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: cockpit-ovirt
Classification: oVirt
Component: gluster-ansible
Version: 0.12.5
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ovirt-4.4.0
: ---
Assignee: Parth Dhanjal
QA Contact: SATHEESARAN
URL:
Whiteboard:
Depends On:
Blocks: 1690820
TreeView+ depends on / blocked
 
Reported: 2019-03-20 09:48 UTC by bipin
Modified: 2020-03-02 07:28 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
: 1690820 (view as bug list)
Environment:
Last Closed: 2020-03-02 07:28:18 UTC
oVirt Team: Gluster
Embargoed:
sasundar: ovirt-4.3?

Attachments (Terms of Use)
UI_Screenshot (131.14 KB, image/png)
2019-03-20 09:55 UTC, bipin 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 99089 0 'None' ABANDONED Disabling FQDN Check for volume creation The volume creation for Day 2 is failing because of gluster_features_fqdn_check... 2020-03-02 07:14:29 UTC

Description bipin 2019-03-20 09:48:17 UTC 
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
Comment 1 bipin 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 bipin 2019-03-20 09:55:32 UTC 
Created attachment 1545990 [details]
UI_Screenshot
Note You need to log in before you can comment on or make changes to this bug.