Description of problem: When using bonding, the ip.sh script only works with slave interfaces which start with eth*. It fails to get status on other bonded interfaces, like for example Infiniband (ib*). Version-Release number of selected component (if applicable): rgmanager-2.0.24-1.el5 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Could you give me 'ip addr list' for a bonded infiniband configuration?
We have decided to run without ib bonding so I can't send you the requested output. The problem seems to be with the /usr/share/cluster/ip.sh script in the findSlaves() function. It only recognizes eth* devices: ---------------------------------------------------------------- while read line; do set - $line while [ $# -gt 0 ]; do case $1 in eth*:) interfaces="${1/:/} $interfaces" continue 2 ;; esac shift done done < <( /sbin/ip link list | grep "master $mastif" ) -------------------------------------------------------------------- Our original configuration had a master device bond1 and 2 slave devices ib0 and ib1.
That's the part I thought was suspect too.
All cluster version 5 defects should be reported under red hat enterprise linux 5 product name - not cluster suite.
Created attachment 296827 [details] Use position rather than pattern-match for slave devices.
Note that link detection won't work on non-ethernet devices anyway, so I'm not sure how much this patch would help.
interfaces=$(/sbin/ip link list | grep "master $mastif" | awk '{print $2}'}) should obviate the need for the loop entirely.
Created attachment 297657 [details] Better patch. Slightly more efficient, and functionally-tested
http://sources.redhat.com/git/?p=cluster.git;a=commit;h=85f99a1f7de8252a73582399194478ad7b2a5845
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2009-0101.html