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

Bug 1715425

Summary: Validation of hosts on first tab
Product: [oVirt] cockpit-ovirt Reporter: bipin <bshetty>
Component: gluster-ansibleAssignee: Parth Dhanjal <dparth>
Status: CLOSED DUPLICATE QA Contact: SATHEESARAN <sasundar>
Severity: medium Docs Contact:
Priority: medium    
Version: 0.12.5CC: bugs, lsvaty, rhs-bugs, sabose, sasundar
Target Milestone: ovirt-4.4.0Flags: sasundar: ovirt-4.3?
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: 1715421 Environment:
Last Closed: 2020-02-17 07:29:02 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: 1715421    

Description bipin 2019-05-30 10:20:32 UTC 
+++ This bug was initially created as a clone of Bug #1715421 +++

Description of problem:
======================
In cockpit the first tab which takes the host hostname/FQDN should have a validation if the FQDN is reachable and then proceed to the next tab.


Version-Release number of selected component (if applicable):
============================================================
RHHI-1.6

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

Steps to Reproduce:
==================
1.
2.
3.

Actual results:
==============


Expected results:
================


Additional info:
===============
Comment 1 SATHEESARAN 2019-05-30 12:36:20 UTC 
Gobinda, 

The thing to consider here is that the FQDN can be DNS resolvable or
available as part of /etc/hosts

Make sure both of the scenario works.

@Bipin, 

New test cases should be:
1. Hostnames with DNS ( usual way of testing ), deployment should be successful
2. Hostnames in /etc/hosts, then deployment should be successful
Comment 3 Parth Dhanjal 2020-02-17 07:29:02 UTC 

*** This bug has been marked as a duplicate of bug 1762800 ***