Bug 762568 (GLUSTER-836)

Summary:	client cannot be mounted from a machine if it does not know the hostnames of servers
Product:	[Retired] GlusterSP	Reporter:	Raghavendra Bhat <rabhat>
Component:	core	Assignee:	Balamurugan Arumugam <bala>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	low
Version:	unspecified	CC:	fharshav, platform, webteam
Target Milestone:	3.0.4
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Raghavendra Bhat 2010-04-20 10:44:36 UTC

In platform the volume files are generated by volgen which puts in the "option remote-host <hostname>" in the client volfile. Suppose a machine tries to mount the exports of the servers on a mount point in it then it fails. Because it pulls the volfile from the storage servers and it cannot resolve the hostname in "option remote-host <hostname>" line to the appropriate IP address, hence fails. Adding the IP address of the server and the corresponding hostname in /etc/hosts file of the client solves it.

Comment 1 Harshavardhana 2010-04-20 13:08:34 UTC

There is no known solution to this. On a cluster you are supposed to know the hostnames. If its required the user can point the nameserver in /etc/resolv.conf to gluster master node i.e first node IP . From which he will be able to get the dns resolved for those hostnames without touching /etc/hosts. 

But in reality this is not an overkill to maintain DNS, people all around the globe maintain 1000's of hostnames in all well known HPC clusters.