Bug 1779525

Summary: [test-only] Allow entry for RHV manager in flat DNS '/etc/hosts'
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: SATHEESARAN <sasundar>
Component: rhhiAssignee: Gobinda Das <godas>
Status: CLOSED ERRATA QA Contact: SATHEESARAN <sasundar>
Severity: medium Docs Contact:
Priority: medium    
Version: rhhiv-1.6CC: asriram, fiezzi, godas, mkalinin, myllynen, rhs-bugs, sasundar, seamurph, shipatil, stirabos, storage-doc
Target Milestone: ---   
Target Release: RHHI-V 1.7   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: 1770920 Environment:
Last Closed: 2020-02-13 15:57:23 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:    
Bug Blocks: 1770920    

Description SATHEESARAN 2019-12-04 06:56:08 UTC 
Describe the issue: 

Above section ask to setup the DNS and resolve Fully-qualified domain names that are forward and reverse resolvable by DNS  which  are required for all hyper-converged hosts and for the Hosted Engine virtual machine that provides Red Hat Virtualization Manager. 

Suggestions for improvement: 

Add information to use flat DNS entry instead of DNS server when customer doing single host isolated installation

Additional information: 

Customer is doing deploying RHHI-V to possibly hundreds of isolated edge clusters (locations) where there is no data center infra and services like external DNS available. In fact, often the RHHI-V nodes are the very first nodes that are being setup in these environments so deployments must be fully self-supporting meaning that customer cannot expect an external DNS being available.

Due to this customer is adding all the RHV Hosts and RHV-M systems to '/etc/hosts' on each and every system in the cluster. With RHHI-V 1.5 this worked just fine, both installation and operation. However, due to installer changes in RHHI-V 1.6 we need to remove RHV-M from /etc/hosts prior RHV-M deployment.

While the above is technically doable for customer, it would seem to indicate that there has not been much testing for RHHI-V deployments without an external DNS service.

Thus customer would like to have isolated edge RHHI-V installations without external DNS to be documented to make sure the product has the needed flexibility for these use cases and to make sure customer is using the most suitable process for deployments here.
Comment 2 SATHEESARAN 2019-12-31 11:14:12 UTC 
Tested with RHV 4.3.8 and RHGS 3.5.1 for RHHI-V 1.7

1. RHHI-V Nodes are configured to use static IPs
2. Front-end and back-end network are configured to use static IPs
3. Network configuration files are edit to have :
<snip>
IPADDR=x.x.x.x
DNS1=x.x.x.x
DNS2=x.x.x.x
PREFIX=N
BOOTPROTO=none
GATEWAY=x.x.x.x
</snip>
4. RHHI-V deployment is initiated using the IPs
5. For HE deployment, HE FQDN is added to /etc/hosts with the corresponding IP
6. Network test is selected as 'PING' instead of 'DNS'

Observed that the HE deployment was successful
Comment 4 errata-xmlrpc 2020-02-13 15:57:23 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:0508