Red Hat Bugzilla – Bug 165447
ip.sh fails when using VLAN (802.1q) on bonded interface
Last modified: 2009-04-16 16:17:56 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (compatible; Konqueror/3.3; Linux) (KHTML, like Gecko)
Description of problem:
When using tagged-VLAN (802.1q) on a bonded interface (eg. dev "bond0.2")
ip.sh fails to find the slaves for this interface (function findSlaves() ) and
therefore can't "start" an IP on it.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Setup VLAN on a bonded interface. (eg. ifcfg-bond0.2)
2. In "Cluster Configuration" setup an IP resource for this interface
3. Start a Service with this resource
Actual Results: Service fails to start:
clurgmgrd: <notice> start on ip "220.127.116.11" returned 1 (generic error)
The following simple hack could solve the problem:
--- [SNIP] ---
--- /usr/share/cluster/ip.sh.old 2005-08-09 16:36:45.772707459 +0200
+++ /usr/share/cluster/ip.sh 2005-08-09 16:38:36.327944199 +0200
@@ -436,6 +436,10 @@
+ ## Strip possible VLAN (802.1q) suffixes
+ ## - Roland Gadinger <firstname.lastname@example.org>
while read line; do
set - $line
while [ $# -gt 0 ]; do
--- [SNIP] ---
Thanks for the patch!
Patch in CVS. Thanks!
Fixes in CVS ready for QA.
Branches: head, STABLE, RHEL4
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 the 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.