Bug 762148 (GLUSTER-416)

Summary:	dnsmasq ignores the management server as dnsserver
Product:	[Retired] GlusterSP	Reporter:	Harshavardhana <fharshav>
Component:	core	Assignee:	Balamurugan Arumugam <bala>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	low
Version:	unspecified	CC:	cww, platform
Target Milestone:	---
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:
Bug Depends On:
Bug Blocks:	762150

Description Harshavardhana 2009-11-28 06:36:25 UTC

nsmasq ignores the management server as dnsserver and instead if we leave "127.0.0.1" default during installation.

"127.0.0.1" gets populated on all "/etc/resolv.conf" on each nodes during installation which leads to lot of no dns resolution and node doesn't come up. 

This can be seen in the management node "/var/log/messages" that dnsmasq clearly throws out a message saying ignoring local ip for nameserver. This needs to be 
fixed as this will lead to problems when starting volumes.

Comment 1 Harshavardhana 2009-12-01 02:41:33 UTC

Wrote the whole functionality supporting this, need to test this on AvailMedia

Comment 2 Harshavardhana 2009-12-01 02:42:26 UTC

oops sorry, not this ticket.. that was for 415