Bug 762148 (GLUSTER-416) - dnsmasq ignores the management server as dnsserver
Summary: dnsmasq ignores the management server as dnsserver
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: GLUSTER-416
Product: GlusterSP
Classification: Retired
Component: core
Version: unspecified
Hardware: All
OS: Linux
low
high
Target Milestone: ---
Assignee: Balamurugan Arumugam
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: GLUSTER-418
TreeView+ depends on / blocked
 
Reported: 2009-11-28 06:36 UTC by Harshavardhana
Modified: 2015-03-23 01:03 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

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
Note You need to log in before you can comment on or make changes to this bug.