Bug 144821 - clumanager goes bonkers if bonding configuration is broken
clumanager goes bonkers if bonding configuration is broken
Status: CLOSED NOTABUG
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-01-11 14:18 EST by Lon Hohberger
Modified: 2009-04-16 16:16 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-01-11 14:18:55 EST
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-01-11 14:18:46 EST
Description of problem:
Clumanager gains/loses quorum consistently on one node.

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

How reproducible:
100%

Steps to Reproduce:
1. Configure a bonded interface.
2. Connect one of the bonded interface cables to the WRONG network so
that ethtool shows that there's a link, but the traffic is dead-ended
(testing was done with a crossover cable).
3. Configure clumanager to use the bonded interface's IP as the member
name.
4. Configure clumanager in 2-node mode and use an IP tiebreaker which
is only reachable via the bonded IP address's route.
5. Set permanent soft quorum with "cludb -p cluquorumd%allow_soft 1".
6. Start clumanager on that node.
  
Actual results:
Clumanager quorum forms/dissolves continually.


Expected results:
Unknown.


Additional info:
This is a configuration problem, not a clumanager problem.  When
pinging the IP tiebreaker in this configuration, the following output
is received:

[root@magenta network-scripts]# ping 192.168.1.254
PING 192.168.1.254 (192.168.79.254) 56(84) bytes of data.
64 bytes from 192.168.1.254: icmp_seq=1 ttl=255 time=0.282 ms
64 bytes from 192.168.1.254: icmp_seq=3 ttl=255 time=0.336 ms
64 bytes from 192.168.1.254: icmp_seq=5 ttl=255 time=0.302 ms
64 bytes from 192.168.1.254: icmp_seq=7 ttl=255 time=0.278 ms
64 bytes from 192.168.1.254: icmp_seq=9 ttl=255 time=0.326 ms
64 bytes from 192.168.1.254: icmp_seq=11 ttl=255 time=0.463 ms

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