Bug 1396029

Description of problem:

Adding a new bridge connection via Network Manager GUI under Gnome adds a bridge but it is never started. 

This is exactly the same of Bug 1036961 which was closed due to Fedora 21 EOL but it's still around on F24.

Plus, the suggestion to bring the bridge slave up via nmcli does not work anymore.


Version-Release number of selected component (if applicable):

1.2.4-3.fc24


How reproducible:
Always

Steps to Reproduce:
Click Network in Gnome Settings
Click the Plus button in the lower left
Click Bridge
I see a dialog called "Editing Bridge connection 1". Next to the "Bridged Connections" panel, click the "Add" button. I expect this to add an existing interface to the bridge.
A dialog appears that says "Select the type of connection you wish to create" - I want to add an ethernet connection to the bridge, so I select "Ethernet" in the dropdown. The options are "Create..." and "Cancel". I click "Create..."
This opens a dialog titled "Editing bridge0 slave 1". The options are "Device MAC address", "Cloned MAC address", and "MTU".
Now, as an average user, I'm pretty lost but let's try to take a guess...
In the "Device MAC address" I click the dropdown arrow. I see the MAC address of my ethernet device with "(enp0s31f6)" next to it. I select it. 
I click "Save..."
I am back in the "Editing Bridge connection 1" dialog. I click "Save..." (I'm aware I have added only one interface, but lets see if that works).
I click "Save..." in the bridge dialog.

Actual results:

I have a bridge. It can never establish a connection. It seems to have no interfaces connected.

$ brctl show
bridge name	bridge id		STP enabled	interfaces
bridge0		0080.000000000000	yes		


Expected results:

A bridge is created and associated with the ethernet device indicated in the set up dialog.

Additional info:

The bridge can be set up by forcing its state up with nmcli:

$ nmcli con show
NAME                       UUID                                  TYPE             DEVICE    
Bridge connection 1        39b61f8f-d5c4-4d90-88e2-bb497cfd4744  bridge           bridge0   
enp0s31f6                  4a104510-8889-4db2-bc97-fe523a18ae99  802-3-ethernet   enp0s31f6 
bridge0 slave 1            825fd23b-5ca0-4978-b35c-4313128f5e3a  802-3-ethernet   --        

Then, I try to set the slave up but there's no way to do it:

$ nmcli con up 825fd23b-5ca0-4978-b35c-4313128f5e3a
Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/5)

But why should a user use the GUI and then CLI?