From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9b5) Gecko/2008043010 Fedora/3.0-0.60.beta5.fc9 Firefox/3.0b5 Description of problem: Problem Description: RGmanager IP resources will not work on Xen dom0 systems whose bonded interfaces is bridged following these instructions: http://kbase.redhat.com/faq/FAQ_103_11147.shtm using netdev=bondX. For example on a Xen system that has bond0 bridged for its guests, the actual interfaces that is the master of the slaves is pbond0. The /usr/share/cluster/ip.sh script will fail to find the slaves because it looks for them on bond0. The problem is in the findSlaves() function (line 462) where it finds the slaves using /sbin/ip link list | grep "master $mastif" where $mastif = bond0. However on a xen system, the slave interfaces list pbond0 as their master: [root@johnny5 ~]# /sbin/ip link list | grep "master bond0" [root@johnny5 ~]# /sbin/ip link list | grep "master pbond0" 2: eth0: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master pbond0 qlen 1000 3: eth1: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master pbond0 qlen 1000 This results in an error when the first status check is run on the ip address: Jun 9 12:31:07 helios clurgmgrd[30493]: <notice> Starting stopped service service:Eprisa Jun 9 12:31:07 helios clurgmgrd: [30493]: <err> Error determining status of bond0 Jun 9 12:31:07 helios clurgmgrd: [30493]: <err> Error finding slaves of bond0 Jun 9 12:31:07 helios clurgmgrd[30493]: <notice> start on ip "192.168.69.76" returned 1 (generic error) Jun 9 12:31:07 helios clurgmgrd[30493]: <warning> #68: Failed to start service:Eprisa; return value: 1 Version-Release number of selected component (if applicable): rgmanager-2.0.38-2 How reproducible: Always Steps to Reproduce: 1) Create a cluster of dom0's 2) Create a bonded interface 3) Bridge the bonded interface using above kbase 4) Create service with ip on the subnet of the bonded interface 5) Start service Actual Results: Service starts but first status check fails saying <err> Error determining status of bond0 <err> Error finding slaves of bond0 Expected Results: Service should start and status checks should succeed Additional info:
Created attachment 309504 [details] Patch to allow vips on bonded interface On a xen systems, the actual interface that is listed as the master of the slaves is pbond0. The ip script checks for slaves on bondX however and fails. This patch fixes that issue.
Hi Shane, Has this been tested on bonded interfaces w/o Xen as well? If not, it's something we need to test. If so, I can apply immediately.
Created attachment 309523 [details] Patch to allow vips on bonded interface
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release.
http://sources.redhat.com/git/?p=cluster.git;a=commit;h=15ae6919dd7c33b1b6746c12a1170c794e736f52
Patch is in tree.
gfs2-utils-2.03.05-1.fc9, rgmanager-2.03.05-1.fc9, cman-2.03.05-1.fc9 has been pushed to the Fedora 9 stable repository. If problems still persist, please make note of it in this bug report.
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