Bug 1316592

(Probably related to bug 1316488.)
 
Description of problem:
After creating a new bond, the AvailableConnections property of the new device remains empty.  This means that Cockpit does not find the slave connections for the bridge, and doesn't show the slave interfaces correctly.

AvailableConnections seems to have the wrong value a lot, and that causes trouble in general for Cockpit.  If AvailableConnections is not reliable, we would have to match connections with devices ourselves, which would suck of course.

Version-Release number of selected component (if applicable):
NetworkManager-1.2.0-0.6.beta2.fc24.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Get to a clean setup with one extra network interface

# nmcli device 
DEVICE  TYPE      STATE         CONNECTION         
ens3    ethernet  connected     Wired connection 1 
ens9    ethernet  disconnected  --                 
lo      loopback  unmanaged     --                

# nmcli connection 
NAME                UUID                                  TYPE            DEVICE 
Wired connection 1  5845fe78-e280-43be-9839-9a0c76317aa0  802-3-ethernet  ens3   


2.  Create a bond by creating two new connection settings

# nmcli connection add type bond con-name BOND
# nmcli connection add type bond-slave con-name ens9 master BOND ifname ens9

# nmcli device show nm-bond

3. Check the AvailableConnections property

# gdbus introspect -y -d org.freedesktop.NetworkManager -o /org/freedesktop/NetworkManager/Devices/3

Actual results:
      readonly ao AvailableConnections = [];


Expected results:
      readonly ao AvailableConnections = [ path-to-BOND-connection-settings ];