|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0011138||CentOS-7||[All Projects] general||public||2016-07-07 07:16||2016-10-05 15:16|
|Target Version||Fixed in Version|
|Summary||0011138: Bridge device cannot get ip from dhcp when connected to teamed device (no link available). After restart of network - works|
|Description||2 Ethernet devices are configured in a team (activebackup) and a network bridge is connected to the team device.|
After a reboot (NetworkManager.service is masked) the network.service reports that the team device is up , but there is no link for the bridge. After "ystemctl restart network" the bridge receives it's ip.
When the bridge is set to static ip - it always works.
|Steps To Reproduce||Connect a bridge device to a team device(activebackup runner)with masked NetworkManager.service. Static IPs in the configs (commented) always work.|
|Additional Information||Config of ifcfg-team0-eth0:|
Config of ifcfg-team0-eth1:
Config of the team device (ifcfg-team0):
Config of the bridge (ifcfg-br0):
|Tags||No tags attached.|
I was able to replicate this issue and have resolved it with a patch that I will attach momentarily.
The issue was that, if DELAY is not set in ifcfg-br0, the init script would not wait for STP to complete startup before attempting to obtain an IP via DHCP.
DELAY is now set by obtaining the forward_delay directly from the interface if DELAY is not otherwise defined.
Let me know if you have any questions or concerns about this patch.
-Rich Alloway (RogueWave)
Will it be provided in the next version of the package ,as I'm not allowed to manually patch the scripts?
Is it affecting RHEL 7 also ? Should I report it there , too - as I have a mixed environment of CentOS/RHEL 7 servers ?
Yes, RHEL 7 will exhibit the same behavior. The file which the patch modifies is included in the source tarball used to build the RPM, so RHEL and CentOS would be impacted equally.
I can open a ticket with RedHat referencing this ticket, or, if you'd prefer, you can open the ticket and I'll update it with my patch.
If the patch is accepted by RedHat, the fix should be included in a future package release, but it is anyone's guess as to when that may be.
Feel free to shoot me an email (email@example.com) if you want to discuss getting a RPM.
-Rich Alloway (RogueWave)
Feel free to open a ticket to Red Hat, in order to help anyone else in the same situation.It seems our subscription with Red Hat is "self-support" and this type of subscription does not bring support on any Operating System related issue.
I'll modify the "ifcfg-br0" to impose a DELAY ,as I'm not allowed to manually patch the "initscripts" in order to easily recognize patched from non-patched version.
The best option would be Red Hat to review the patch ,that you have proposed, so they can add it in a future package.
|I have created a new bug report in the RedHat Bugzilla referencing this ticket and supplied my patch: https://bugzilla.redhat.com/show_bug.cgi?id=1380496|
|2016-07-07 07:16||hunter86_bg||New Issue|
|2016-07-07 07:16||hunter86_bg||File Added: journalctl-network.service_unix.txt|
|2016-09-28 21:10||N3WWN||Note Added: 0027612|
|2016-09-28 21:10||N3WWN||File Added: initscripts-9.49.30-1.el7_2.3_bugs.centos.org_11138.patch|
|2016-09-29 12:06||hunter86_bg||Note Added: 0027614|
|2016-09-29 15:21||N3WWN||Note Added: 0027622|
|2016-09-29 15:59||hunter86_bg||Note Added: 0027625|
|2016-09-29 18:58||N3WWN||Note Added: 0027626|