Description of problem: Version-Release number of selected component (if applicable): 3.15.4-200.fc20.x86_64 #1 SMP Mon Jul 7 14:24:41 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux All latest updates as of July 11 applied to the system. How reproducible: Create a Bridge for use by KVM virtual machines, as per Avi Alkalay's blog: http://avi.alkalay.net/2014/01/fedora-20-virtualization-networkmanager-native-bridge.html Actual results: After a poweroff (but not after a reboot), the slave ethernet connection is no longer assoiciated with the Bridge master. ifconfig shows that the bridge is not recieving an ipv4 address. Expected results: Poweroff should not break the link between the Bridge and its slave ethernet connection. Additional info:
It appears that the bridge is broken on a poweroff only if the bridge was assigned de facto to the list of network interfaces in the Virtual Machines Manager Connection Details.
When I poweroff and restart - I get the following message in the NetworkManager log: Master connection not found or invalid
The bridge slave profile is linked to the bridge master by 'connection.master' property. It can contains UUID of master connection or interface name of the bridge. nm-connection-editor uses UUID by default. So I guess something (libvirt UI) changed or removed the master bridge profile or something. You can list the profiles to see if they are there $ nmcli con show conf and then grab the details of the master and slave profiles $ nmcli con show conf 'your bridge master' $ nmcli con show conf 'your bridge slave' It would help if you could attach NetworkManager logs, too (/var/log/messages or journalctl).
Created attachment 921914 [details] Output of Journalctl after the poweroff/poweron
Created attachment 921918 [details] Output of $nmcli con show immediately after creating bridge Output of $nmcli con show immediately after creating bridge, but before assigning it to the virtual manager list of Network Interfaces
Created attachment 921919 [details] Output of $nmcli con show for the Master immediately after creating bridge Output of $nmcli con show for the Master immediately after creating bridge, but before assigning it to the virtual manager list of Network Interfaces
Created attachment 921920 [details] IGNORE THIS ATTACHMENT - MISTAKENLY UPLOADED Output of $nmcli con show for the Slave immediately after creating bridge, but before assigning it to the virtual manager list of Network Interfaces
Created attachment 921921 [details] Output of $nmcli con show for the Slave immediately after creating bridge Output of $nmcli con show for the Slave immediately after creating bridge, but before adding it in Virtual Manager to the list of Network Interfaces
Created attachment 921922 [details] Output of $nmcli con show after adding the bridge to the list of Network Interfaces in Virtual Manager Output of $nmcli con show after adding the bridge to the list of Network Interfaces in Virtual Manager, but before poweroff/poweron.
Created attachment 921923 [details] Output of $nmcli con show for the Master after adding the bridge to the list of Network Interfaces in Virtual Manager Output of $nmcli con show for the Master after adding the bridge to the list of Network Interfaces in Virtual Manager, but before poweroff/poweron.
Created attachment 921924 [details] Output of $nmcli con show for the Slave after adding the bridge to the list of Network Interfaces in Virtual Manager Output of $nmcli con show for the Slave after adding the bridge to the list of Network Interfaces in Virtual Manager, but before poweroff/poweron.
Created attachment 921925 [details] Output of $nmcli con show after poweroff/poweron Output of $nmcli con show after poweroff/poweron.
Created attachment 921926 [details] Output of $nmcli con show for the Master after poweroff/poweron. Output of $nmcli con show for the Master after poweroff/poweron.
Created attachment 921927 [details] Output of $nmcli con show for the Slave after poweroff/poweron. Output of $nmcli con show for the Slave after poweroff/poweron.
Comment on attachment 921920 [details] IGNORE THIS ATTACHMENT - MISTAKENLY UPLOADED IGNORE THIS ATTACHMENT - MISTAKENLY UPLOADED
(In reply to Jirka Klimes from comment #3) > The bridge slave profile is linked to the bridge master by > 'connection.master' property. It can contains UUID of master connection or > interface name of the bridge. nm-connection-editor uses UUID by default. > So I guess something (libvirt UI) changed or removed the master bridge > profile or something. > > You can list the profiles to see if they are there > $ nmcli con show conf > > and then grab the details of the master and slave profiles > $ nmcli con show conf 'your bridge master' > $ nmcli con show conf 'your bridge slave' > > It would help if you could attach NetworkManager logs, too > (/var/log/messages or journalctl). Hi Jirka - I provided the info you requested. I noticed that I called the bridge "bridge0", whereas Avi Alkalay called his "bridge1" ( http://avi.alkalay.net/2014/01/fedora-20-virtualization-networkmanager-native-bridge.html ) I can only assume that this is irrelevant. TIA, Lavie
(In reply to Jirka Klimes from comment #3) > The bridge slave profile is linked to the bridge master by > 'connection.master' property. It can contains UUID of master connection or > interface name of the bridge. nm-connection-editor uses UUID by default. > So I guess something (libvirt UI) changed or removed the master bridge > profile or something. > > You can list the profiles to see if they are there > $ nmcli con show conf > > and then grab the details of the master and slave profiles > $ nmcli con show conf 'your bridge master' > $ nmcli con show conf 'your bridge slave' > > It would help if you could attach NetworkManager logs, too > (/var/log/messages or journalctl).
Jirka Klimes: Any news?
Could this be related? https://www.happyassassin.net/2014/07/23/bridged-networking-for-libvirt-with-networkmanager-2014-fedora-21/
Sorry for the late reply. I was on holiday. The issue is that the bridge master connection changed after the poweroff. See the difference in comment #5 and comment #12: Bridge connection 1 (bf0dddae-ac97-4530-a31f-a2a553333a66) - comment #5 Bridge bridge0 (6ae67f40-dd39-36a5-edae-2d28e83a4a5c) - comment #12 In the logs you can see that the connection had come from file /etc/sysconfig/network-scripts/ifcfg-Bridge_connection_1, but after reboot there was /etc/sysconfig/network-scripts/ifcfg-bridge0. So the original ifcfg file was removed (or renamed) and there is a new one. What is the content of the files? Because the 'Bridge bridge0' connection has different UUID than 'Bridge connection 1', and the slave refers to the old UUID, the master cannot be found. You could use 'bridge0' in slave's connection.master property (BRIDGE=bridge0 in ifcfg file) instead of the UUID. However, it would be good to track what happened to the original ifcfg file and why there is the new one. I think you didn't edit the files manually. Right? (In reply to Lavie from comment #19) > Could this be related? > > https://www.happyassassin.net/2014/07/23/bridged-networking-for-libvirt-with- > networkmanager-2014-fedora-21/ It is probably not directly related, but it is a nice post testing various cases with bridges.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
This appears to be fixed in Fedora 21. Unfortunately, Fedora 21's default gnome does not include the nm-connection-editor applet, which makes life much easier for defining a bridge.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.