Bug 489771 - dhclient runs on bridge interface before physical interfaces are added
dhclient runs on bridge interface before physical interfaces are added
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: initscripts (Show other bugs)
All Linux
low Severity medium
: rc
: ---
Assigned To: initscripts Maintenance Team
Depends On:
  Show dependency treegraph
Reported: 2009-03-11 15:03 EDT by Ray Van Dolson
Modified: 2009-03-18 16:44 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-03-18 16:44:43 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Patch against RHEL4 inittscripts to fix bridge behavior (3.45 KB, patch)
2009-03-11 15:03 EDT, Ray Van Dolson
no flags Details | Diff

  None (edit)
Description Ray Van Dolson 2009-03-11 15:03:09 EDT
Created attachment 334849 [details]
Patch against RHEL4 inittscripts to fix bridge behavior

See #125259.

Description of problem:
If we configure a bridge to use DHCP, dhclient gets called on the bridge interface before member interfaces have been added to it.

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

How reproducible:

Steps to Reproduce:
1. Set up a bridge br0 and configure it to use DHCP
2. Configure physical interface, eth0 as a bridge member.
3. Restart server
Actual results:
No IP address is acquired on br0.

Expected results:
IP address should be acquired on br0.

Additional info:
This can be fixed by applying the attached patch.  This has been fixed in Fedora, and may or may not still be an issue in RHEL5 (haven't checked).  It should be corrected in both.
Comment 1 Bill Nottingham 2009-03-18 16:44:43 EDT
     This problem is resolved in the next major release of Red Hat Enterprise Linux. Red Hat does not currently plan to provide a resolution for this in a RHEL 4 update for currently deployed systems.

    With the goal of minimizing risk of change for deployed systems, and in response to customer and partner requirements, Red Hat takes a conservative approach when evaluating changes for inclusion in maintenance updates for currently deployed products. The primary objectives of update releases are to enable new hardware platform support and to resolve critical defects.

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