Red Hat Bugzilla – Bug 1304495
bond slaves are not connected automatically after creation when device was disconnected manually
Last modified: 2016-04-29 08:25:20 EDT
Description of problem:
when bond is created with slaves these slaves are not upped. No other way how to up them. This looks like a regression to 7.1.
There is no other way how to up them in control-center or in other gui application.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.open control-center network
2.click plus and select bond
3.set ipv4 to manual and set ip
4.set ipv6 to ignore
5.add slave to ethernet device
bond connected but slave is not
both should be connected
NOTABUG as master was upped by nmcli and this action removes slaves. Closing
reopening just for reconsidering the situation when
1. the device for bond slave was disconnected by nmcli device disconnect
2. the device is not grabbed by NM's autoconnect anymore as it's marked unsuitable for this because of device disconnect
3. do we want to connect it when the bond is created with slave profile?
Support for enterprise networking features will be removed in future versions of GNOME and of RHEL 7.x. We advise that you test Cockpit instead, which is better suited to manipulate enterprise networking feature.
Teaming support for Cockpit is tracked at:
Bonding, bridging and VLAN support are already implemented.