Hide Forgot
Description of problem: OSP 10 includes a newer release of os-net-config which is capable of configuring adapter teaming as an alternate bonding method. However, os-net-config sets NM_CONTROLLED=no on the team interface configuration, and this causes an error message when the team is brought up. The team works if NM_CONTROLLED=yes is put in the ifcfg-teamX file instead. Version-Release number of selected component (if applicable): OSP 10 RC RHEL 7.3 NetworkManager-team.x86_64 1:1.4.0-12.el7 libteam.x86_64 1.25-4.el7 teamd.x86_64 1.25-4.el7 How reproducible: 100% Steps to Reproduce: 1. Configure an adapter team as a bond in NIC config templates 2. Deploy Actual results: The team ifcfg files contain NM_CONTROLLED=no, but when the network service attempts to bring the team up an error occurs. Expected results: The team should be enabled when 'ifup teamX' is run. Additional info: NetworkManager is able to enable the team interface if NM_CONTROLLED is changed to 'yes'. I have opened a related case to track why network service cannot enable bonds here: https://bugzilla.redhat.com/show_bug.cgi?id=1402535
This bugzilla has been removed from the release and needs to be reviewed and Triaged for another Target Release.
Dan - looks like this may have been fixed in RHEL 7.5 with https://bugzilla.redhat.com/show_bug.cgi?id=1415641. Can we mark this as a duplicate?
(In reply to Bob Fournier from comment #3) > Dan - looks like this may have been fixed in RHEL 7.5 with > https://bugzilla.redhat.com/show_bug.cgi?id=1415641. Can we mark this as a > duplicate? Actually, this bug was fixed in RHEL 7.4 in this bug: https://bugzilla.redhat.com/show_bug.cgi?id=1402535 Thanks for pointing out that this bug could be closed.