Created attachment 1238147 [details]
Most recent sosreport

Note that the best way to apply the changes done to a connection is by
reactivating it with:

 nmcli connection up <connection name or uuid>

or using the "Activate a connection" menu of nmtui. If the changes
were made directly on ifcfg files you should tell NM to reload the
connections (before the previous command):

 nmcli connection reload

Restarting NM may causes issues in some cases because NM tries to
detect which connections were previously active and this doesn't
always work correctly. We have planned to rework this area for 7.4 and
change how connections are handled upon restart, see bug 1394579.

Anyway, while the issue is reproducible on RHEL 7.2 (NM 1.0.6-31), it
doesn't happen on RHEL 7.3 (NM 1.4.0-13) as bond slaves properly come
up after the service restart.

Thank you, nmcli con reload and con down/up are working fine.

Is there any chance of getting those NM link detection patches backported to 7.2.z, or are the changes between 1.0.6 and 1.4.0 too large? If it can be done, we'll make a formal z-Stream request.

(In reply to Jamie Bainbridge from comment #4)
> Thank you, nmcli con reload and con down/up are working fine.
> 
> Is there any chance of getting those NM link detection patches backported to
> 7.2.z, or are the changes between 1.0.6 and 1.4.0 too large? If it can be
> done, we'll make a formal z-Stream request.

Sorry, due to the amount of changes between 1.0.6 and 1.4.0, the
commits can't be cleanly backported and require many other patches
that are out of scope for 7.2.z and would compromise stability.

No worries, thank you for the reply. Give me a few days and I'll likely move this one to CLOSED NOTABUG. Needinfo on myself for that.