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

Bug 1932851

Summary: FQDN is not reachable when using perfectly valid, fully reachable FQDN
Product: [oVirt] cockpit-ovirt Reporter: Guillem Liarte <guillem.liarte>
Component: GenericAssignee: Gobinda Das <godas>
Status: CLOSED INSUFFICIENT_DATA QA Contact: SATHEESARAN <sasundar>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 0.14.17CC: arachman, bugs, cshao
Target Milestone: ---Flags: pm-rhel: planning_ack?
pm-rhel: devel_ack?
pm-rhel: testing_ack?
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-09-06 06:44:46 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Gluster RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Perfectly good fqdn in the system fails check in the UI
none
Exerpt from logs and tests none

Description Guillem Liarte 2021-02-25 12:12:15 UTC 
Created attachment 1759268 [details]
Perfectly good fqdn in the system fails check in the UI

Description of problem:

When attempting to deploy HC Gluster via Cockpit, the FQDN check fails, despite the FQDNs being fully resolvable forward and backward and the internal network to be completely routable.

Getting "FQDN is not reachable"

This is similar as in 1679540. 


Version-Release number of selected component (if applicable):cockpit-ovirt-dashboard-0.14.17-1.el8.noarch

from ISO: ovirt-node-ng-installer-4.4.4-2021020810.el8.iso

How reproducible:
100%

Steps to Reproduce:
1. Deploy ovirt-node-ng-installer in compatible hardware, 3 hosts
2. via external IP get to Cockpit
3. Start installation process using a FQDN from internal ( as suggested by dialog box) for data network, we use a VLAN only for data traffic.

Actual results: "FQDN is not reachable"


Expected results: being able to install HC oVIrt/Gluster in 3 nodes.


Additional info:

10.91.197.132 ndoamsel001.home.lab
10.91.197.4 ndoamsel002.home.lab
10.91.196.132 ndoamsel003.home.lab

10.0.1.1 ndoamsel001s.home.lab ndoamsel001s
10.0.1.2 ndoamsel002s.home.lab ndoamsel002s
10.0.1.3 ndoamsel003s.home.lab ndoamsel003s


https://lists.ovirt.org/archives/list/users@ovirt.org/thread/4MQGTTMUIQ7PNJTDYDHW3CTTJ4WRBT4L/

root@ndoamsel001 ]# host ndoamsel001s.home.lab
ndoamsel001s.home.lab has address 10.0.1.1
[root@ndoamsel001 ]# host ndoamsel001v.home.lab
ndoamsel001v.home.lab address 10.0.2.1
[root@ndoamsel001 ]# host ndoamsel001.home.lab
ndoamsel001.home.lab has address 10.91.197.132

[root@ndoamsel001s ~]# host 10.0.1.1
1.1.0.10.in-addr.arpa domain name pointer ndoamsel001s.home.lab.

---

My only guess is that the context in which the FQDNs are checked are those of the client browser and the external IP to reach the management, the system fqdns are NOT checked, and that limits substantially the deploy-ability of oVirt in many cases.

While I agree that fqdns must be correct, the check is not done in the correct context and would only work if the client machine is connecting directly to one of the internal IPs that is going to be used to deploy as.
Comment 1 Guillem Liarte 2021-02-25 15:48:50 UTC 
Created attachment 1759337 [details]
Exerpt from logs and tests

I think I can help to make the fqdn, ip, and interface detection more robust. Write to me if you would like me to lend a hand.
Comment 2 Parth Dhanjal 2021-03-16 06:11:42 UTC 
(In reply to Guillem Liarte from comment #1)
> Created attachment 1759337 [details]
> Exerpt from logs and tests
> 
> I think I can help to make the fqdn, ip, and interface detection more
> robust. Write to me if you would like me to lend a hand.

Hey Guillem!

Have you added the ssh-ids to the machine running cockpit-ovirt?
Comment 3 RHEL Program Management 2021-03-16 06:11:48 UTC 
The documentation text flag should only be set after 'doc text' field is provided. Please provide the documentation text and set the flag to '?' again.
Comment 5 Gobinda Das 2021-09-06 06:44:46 UTC 
Did not get any response from reporter. So closing this as Insufficient data. Please reopen if you are facing same issue in latest version.