Bug 149737 - clumanager starts even if no non-slave interface is available
clumanager starts even if no non-slave interface is available
Status: CLOSED WORKSFORME
Product: Red Hat Cluster Suite
Classification: Red Hat
Component: clumanager (Show other bugs)
3
All Linux
medium Severity medium
: ---
: ---
Assigned To: Lon Hohberger
Cluster QE
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-02-25 16:31 EST by Lon Hohberger
Modified: 2009-04-16 16:16 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-09-29 15:47:17 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-02-25 16:31:10 EST
Description of problem:

In an incorrect networking configuration where all physical interfaces
are slaves with no bonding master present, clumanager starts and tries
to run anyway.


Version-Release number of selected component (if applicable): 1.2.22


How reproducible: Unknown


Steps to Reproduce: Unknown

Actual results:

Feb 24 16:36:27 node1 clumembd[6444]: <debug> Multicast address is
225.0.0.11 
Feb 24 16:36:27 node1 clumembd[6444]: <debug> I am member #0 
Feb 24 16:36:27 node1 clumembd[6444]: <debug> Interface IP is 127.0.0.1 
Feb 24 16:36:27 node1 clumembd[6444]: <debug> eth0 is a SLAVE; skipping! 
Feb 24 16:36:27 node1 clumembd[6444]: <debug> eth1 is a SLAVE; skipping! 
Feb 24 16:36:27 node1 clumembd[6444]: <debug> Interface IP is 192.168.0.2 
Feb 24 16:36:27 node1 clumembd[6444]: <debug> Setting up multicast
225.0.0.11 on 192.168.0.2 
Feb 24 16:36:27 node1 clumembd[6444]: <debug> Cluster I/F: eth0
[192.168.0.2] 

Expected results:

Clumanager shouldn't start if no master (and/or only slave) ethernet
devices have the cluster node's IP address bound.
Comment 1 Lon Hohberger 2005-07-11 17:50:30 EDT
Chris, is this related to all the other ARP and bonding routing problems we've
been seeing lately?
Comment 2 Lon Hohberger 2005-07-27 12:44:01 EDT
clumembd checks for IFF_SLAVE during startup -- so does the message service
initialization which is reporting eth0 as the cluster I/F... I can't get this to
happen.

Comment 3 Lon Hohberger 2005-09-29 15:47:17 EDT
This is a network configuration problem - I can't solve them all.

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