[SOLVED] Network Bridge using team - no dhcp

[hunter86_bg]

Hello guys,

here is the situation. I'm training some stuff on CentOS 7.2 (latest updates). Here is the setup:
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

Code: Select all

service network restart

or

Code: Select all

systemctl restart network

the bridge receives it's ip.
When the bridge is set to static ip - it always works.
I think that this is a kind of a bug.

Output from network.service:

Code: Select all

-- Logs begin at Wed 2016-07-06 13:00:06 EEST, end at Wed 2016-07-06 13:07:01 EEST. --
Jul 06 13:00:38 server1.example.com systemd[1]: Starting LSB: Bring up/down networking...
Jul 06 13:00:38 server1.example.com network[996]: Bringing up loopback interface:  [  OK  ]
Jul 06 13:00:40 server1.example.com network[996]: Bringing up interface team0:  [  OK  ]
Jul 06 13:00:40 server1.example.com network[996]: Bringing up interface team0-eth0:  [  OK  ]
Jul 06 13:00:41 server1.example.com network[996]: Bringing up interface team0-eth1:  [  OK  ]
Jul 06 13:00:41 server1.example.com network[996]: Bringing up interface br0:
Jul 06 13:00:48 server1.example.com network[996]: Determining IP information for nm-bridge... failed; no link present.  Check cable?
Jul 06 13:00:48 server1.example.com network[996]: [FAILED]
Jul 06 13:00:48 server1.example.com systemd[1]: network.service: control process exited, code=exited status=1
Jul 06 13:00:48 server1.example.com systemd[1]: Failed to start LSB: Bring up/down networking.
Jul 06 13:00:48 server1.example.com systemd[1]: Unit network.service entered failed state.
Jul 06 13:00:48 server1.example.com systemd[1]: network.service failed.
Jul 06 13:06:56 server1.example.com systemd[1]: Starting LSB: Bring up/down networking...
Jul 06 13:06:56 server1.example.com network[2796]: Bringing up loopback interface:  [  OK  ]
Jul 06 13:06:56 server1.example.com network[2796]: Bringing up interface team0:  RTNETLINK answers: File exists
Jul 06 13:06:56 server1.example.com network[2796]: RTNETLINK answers: File exists
Jul 06 13:06:57 server1.example.com network[2796]: device nm-team is already a member of a bridge; can't enslave it to bridge nm-bridge.
Jul 06 13:06:57 server1.example.com network[2796]: [  OK  ]
Jul 06 13:06:57 server1.example.com network[2796]: Bringing up interface team0-eth0:  RTNETLINK answers: File exists
Jul 06 13:06:57 server1.example.com network[2796]: [  OK  ]
Jul 06 13:06:57 server1.example.com network[2796]: Bringing up interface team0-eth1:  RTNETLINK answers: File exists
Jul 06 13:06:57 server1.example.com network[2796]: [  OK  ]
Jul 06 13:06:57 server1.example.com network[2796]: Bringing up interface br0:
Jul 06 13:06:57 server1.example.com dhclient[3251]: DHCPREQUEST on nm-bridge to 255.255.255.255 port 67 (xid=0x3c9dd4c3)
Jul 06 13:06:57 server1.example.com dhclient[3251]: DHCPACK from 192.168.100.1 (xid=0x3c9dd4c3)
Jul 06 13:07:00 server1.example.com network[2796]: Determining IP information for nm-bridge... done.
Jul 06 13:07:01 server1.example.com network[2796]: [  OK  ]
Jul 06 13:07:01 server1.example.com network[2796]: RTNETLINK answers: File exists
Jul 06 13:07:01 server1.example.com network[2796]: RTNETLINK answers: File exists
Jul 06 13:07:01 server1.example.com network[2796]: RTNETLINK answers: File exists
Jul 06 13:07:01 server1.example.com network[2796]: RTNETLINK answers: File exists
Jul 06 13:07:01 server1.example.com network[2796]: RTNETLINK answers: File exists
Jul 06 13:07:01 server1.example.com network[2796]: RTNETLINK answers: File exists
Jul 06 13:07:01 server1.example.com network[2796]: RTNETLINK answers: File exists
Jul 06 13:07:01 server1.example.com network[2796]: RTNETLINK answers: File exists
Jul 06 13:07:01 server1.example.com network[2796]: RTNETLINK answers: File exists
Jul 06 13:07:01 server1.example.com systemd[1]: Started LSB: Bring up/down networking.

Config of ifcfg-team0-eth0:

Code: Select all

NAME=team0-eth0
UUID=d2cb2d59-0d97-46ef-b5d9-255341a059a2
DEVICE=eth0
ONBOOT=yes
TEAM_MASTER=nm-team
DEVICETYPE=TeamPort

Config of ifcfg-team0-eth1:

Code: Select all

NAME=team0-eth1
UUID=00cec63f-58aa-49d4-8c1b-f4004c0b6c7e
DEVICE=eth1
ONBOOT=yes
TEAM_MASTER=nm-team
DEVICETYPE=TeamPort

Config of the team device (ifcfg-team0):

Code: Select all

DEVICE=nm-team
TEAM_CONFIG="{\"runner\":{\"name\":\"activebackup\"}}"
DEVICETYPE=Team
#BOOTPROTO=dhcp
#DEFROUTE=yes
#PEERDNS=yes
#PEERROUTES=yes
#IPV4_FAILURE_FATAL=no
#IPV6INIT=yes
#IPV6_AUTOCONF=yes
#IPV6_DEFROUTE=yes
#IPV6_PEERDNS=yes
#IPV6_PEERROUTES=yes
#IPV6_FAILURE_FATAL=no
NAME=team0
UUID=e28b33c4-d175-4c36-9f3d-6b4c6d24453f
ONBOOT=yes
BRIDGE=nm-bridge

Config of the bridge (ifcfg-br0):

Code: Select all

DEVICE=nm-bridge
STP=yes
BRIDGING_OPTS=priority=32768
TYPE=Bridge
#BOOTPROTO=static
BOOTPROTO=dhcp
DEFROUTE=yes
PEERDNS=yes
PEERROUTES=yes
IPV4_FAILURE_FATAL=no
IPV6INIT=yes
IPV6_AUTOCONF=yes
IPV6_DEFROUTE=yes
IPV6_PEERDNS=yes
IPV6_PEERROUTES=yes
IPV6_FAILURE_FATAL=no
NAME=br0
UUID=25f33bab-f987-4ccf-b49b-a072957c2fe3
ONBOOT=yes
#IPADDR0=192.168.100.151
#PREFIX0=24

Do you think that this behaviour is an indication of a bug , or it is a misconfiguration ?

Thank you all for reading this long post.

[hunter86_bg]

For anyone interested - this bug was confirmed and a patch was proposed.For details:Teamd and Bridge - no dhcp

[TrevorH]

Unless you raise a bugzilla entry on bugzilla.redhat.com and get this patch accepted by them, it will go nowhere.

[hunter86_bg]

Thanks Trevor,

I have asked N3WWN to report it to Red Hat.Report in Bugzilla: Bugzilla
For anyone in the same situation - a possible solution is to set a "DELAY" in the bridge config.

[hunter86_bg]

A short Necro.
This bug is resolved now via RHBA-2018:0983