To ensure that people aren't surprised by the new support for these connections, we want to disable this functionality by default and only enable it when a key in a config file is set.
This request was evaluated by Red Hat Product Management for inclusion
in a Red Hat Enterprise Linux maintenance release. Product Management has
requested further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update release.
The mechanism is that NM will now read NM_BOND_VLAN_ENABLED in /etc/sysconfig/network. If and only if that key is present and is one of "yes", "y", or "true", will NetworkManager detect and manage bonding and vlan interfaces.
If that key is missing or "no"/"false", you should *not* see NetworkManager do any of the following:
1) detect and manage bonding or VLAN interfaces
2) create bonding or VLAN interfaces as a result of writing a bond/vlan ifcfg file to /etc/sysconfig/network-scripts
3) successfully activate a bond/VLAN connection when initiated via 'nmcli con up uuid <uuid of bond/vlan connection>"
NM will still parse and read bond/vlan ifcfg files, but it will simply ignore any bond/vlan interfaces and should not create them unless NM_BOND_VLAN_ENABLED=yes.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.