Bug 159007 - RFE: Have CMAN detect use of loopback address and refuse to run
RFE: Have CMAN detect use of loopback address and refuse to run
Status: CLOSED ERRATA
Product: Red Hat Cluster Suite
Classification: Red Hat
Component: cman (Show other bugs)
4
All Linux
medium Severity high
: ---
: ---
Assigned To: Christine Caulfield
Cluster QE
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-05-27 12:05 EDT by Lon Hohberger
Modified: 2009-04-16 15:59 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-10-17 10:40:53 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Lon Hohberger 2005-05-27 12:05:54 EDT
Description of problem:

When using 2-node clusters and /etc/hosts is improperly configured in such a way
that the local node name resolves to a loopback address, a split-brain can ensue.

Thus, it would be nice if, when starting, CMAN could check for the improper use
of loopback and abort/not run if this occurs (as well as printing a loud warning).

While the case where this would cause problems in production is probably
astronomically low (this is not a BUG, it's a feature request), it does and has
caused confusing for new installations when configuring the cluster for the
first time.
Comment 1 Lon Hohberger 2005-05-27 12:08:30 EDT
...it does and has caused confusion when configuring the cluster for the
first time.

Making sense is a good thing.

Comment 2 Markus Jeckeln 2005-05-27 12:23:42 EDT
Yes... my installation of RHEL 4 came up with my hostname in /etc/hosts at the
loopback address that came up with the cluster confusion. 

samples on node1

config sample: notworking
127.0.0.1               mynode1 localhost.localdomain localhost
192.168.0.105           mynode2
192.168.0.104           mynode1  #added by myself since i had probs with the cluster

config sample fixed & working
127.0.0.1               localhost.localdomain localhost
192.168.0.105           mynode2
192.168.0.104           mynode1

good thing would me a note in syslog or something like that

greeeeetz markus.jeckeln@gmx.de
Comment 3 Christine Caulfield 2005-05-31 11:08:49 EDT
Added to CVS head and FC4 branches.
Comment 4 Christine Caulfield 2005-06-28 08:37:19 EDT
Added to RHEL4 branch so it should appear in U2

Note You need to log in before you can comment on or make changes to this bug.