Bug 159500
| Summary: | Bug in ifup script brings down bonding slaves | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 4 | Reporter: | Michael Brown <michael> | ||||||
| Component: | initscripts | Assignee: | Bill Nottingham <notting> | ||||||
| Status: | CLOSED DUPLICATE | QA Contact: | Brock Organ <borgan> | ||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | medium | ||||||||
| Version: | 4.0 | CC: | frank.solem, rvokal, shillman, troels, trondham | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | All | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2008-12-08 21:59:21 UTC | Type: | --- | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
|
Description
Michael Brown
2005-06-03 02:12:07 UTC
Created attachment 115123 [details]
bond0 config
Created attachment 115124 [details]
eth0 config
Anybody out there? It's been 3 weeks since I reported this regression. I couldn't reproduce it in brief testing here; need to try some more. I've noticed odd behaviour - it only generates the abberrant behaviour on reboot. On a hunch, what happens if you try the current beta hotplug & initscripts packages? initscripts-7.93.20.EL-1 hotplug-2004_04_01-7.6 We see this too. On a machine with two bonded interfaces (i.e. four real devices) one of the real devices gets a down state. Running '/sbin/ip link set dev eth0 up' sets its link status to up. The weird thing is that we only see this on one of the four real devices, even though they are all slaves. The relevant lines from modprobe.conf on this box: alias eth0 e1000 alias eth1 e1000 alias eth2 tg3 alias eth3 tg3 install bond0 /sbin/modprobe -a eth1 eth3 && /sbin/modprobe bonding alias bond0 bonding install bond1 /sbin/modprobe -a eth0 eth2 && /sbin/modprobe bonding alias bond1 bonding options bonding mode=1 miimon=100 max_bonds=2 It's eth0 that gets its link state set to down. One additional note: Failover to eth0 does not work unless we manually set its link state to up. I had trouble somewhat resembling this bug's description. I didn't change any scripts, but I adjusted the value of max_bonds to 4; this allowed me to have four NICs in two bonds. I am also experiencing problems with bonding interfaces downing the slaves. The
error state is that both slave interfaces will remain in a link-down state until
networking is restarted. To produce this result a certain set of circumstances
must occur (which makes it hard to reproduce reliably). The circumstances as I
have observed are that the e1000 driver is loaded and ifup executes "/sbin/ip
link set dev ${DEVICE} down" *before* the interface is able to establish link to
the switch. If this happens then when the bonding driver is loaded and
interfaces are enslaved the physical interfaces never seem to get link
automatically and will remain down. This will only happen if you hard power
cycle the machine or pull the links from the switch, a warm reboot seems to
bypass the problem by not loosing link with the switch.
Workarounds...
If you execute an "ip set link dev blah up" the interfaces will immediately get
link. It's also possible to work around by putting a sleep in the ifup-local so
that the enslaved interfaces are able to get link on the switch prior to be
downed by the ifup script and enslaved. And one more workaround is to change "ip
link down" to "ip link up" in the ifup script as the bug sumbitter suggested.
--Dave P.
This sounds very similar to 432622. Does the fix there work for you? *** This bug has been marked as a duplicate of bug 432622 *** |