[Bug 1432599] Re: Network-manager tries to manage virbr0, which it should not
Launchpad has imported 26 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=1166199. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2014-11-20T14:55:32+00:00 Richard wrote: Description of problem: Since I upgraded to Fedora 21, NetworkManager is now offering to manage virbr0. In fact, if I disconnect from wireless, then it falls back to "helpfully" connecting me to virbr0, which is of course completely useless. More seriously, I suspect that NM is actually breaking virbr0. For some reason, virbr0-nic became disconnected from the virbr0 bridge, and that broke all libvirt networking, and I suspect this happened about the time that NM decided to connect my main network to virbr0. I've no idea what we can do about this, or even which component this belongs to. On my machine I tried adding: NM_CONTROLLED=no to /etc/sysconfig/network-scripts/ifcfg-virbr0 although this has so far not made any difference (but I haven't rebooted yet). Version-Release number of selected component (if applicable): libvirt-1.2.9-4.fc21.x86_64 NetworkManager-0.9.10.0-13.git20140704.fc21.x86_64 How reproducible: 100% Steps to Reproduce: 1. Use Fedora 21 and libvirt and NM. Reply at: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/1432599/comments/0 On 2015-01-09T21:55:24+00:00 Aleksandar wrote: Any update on this? It's been close to 2 months. I just performed a fedup to 21 and I hit the same issue. My em1 device remains disconnected and virbr0 is shown connected but of course I can't get internet through it. Good that at least wifi works though. Reply at: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/1432599/comments/1 On 2015-01-09T22:11:14+00:00 Aleksandar wrote: looks like re-occurrence of bug 1063545 and bug 1064441 I'm changing product and version to fedora21 as it looks like a network manager issue. Reply at: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/1432599/comments/2 On 2015-01-09T22:40:56+00:00 Aleksandar wrote: Created attachment 978433 log from systemctl restart NetworkManager I've got rid of virbr0 device by putting into /etc/NetworkManager/NetworkManager.conf the following content: > [keyfile] > unmanaged-devices=interface-name:virbr0 It also should support unmanaged-devices=mac:... But I still can't get em1 to connect. Attaching what I get from /var/log/messages on NetworkManager service restart. Reply at: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/1432599/comments/3 On 2015-01-09T22:47:23+00:00 Aleksandar wrote: Forgot to say that running dhcp manually brings up the interface just fine: > $ sudo dhclient -d em1 > Internet Systems Consortium DHCP Client 4.3.1 > Copyright 2004-2014 Internet Systems Consortium. > All rights reserved. > For info, please visit https://www.isc.org/software/dhcp/ > > Listening on LPF/em1/3c:97:0e:19:30:f9 > Sending on LPF/em1/3c:97:0e:19:30:f9 > Sending on Socket/fallback > DHCPREQUEST on em1 to 255.255.255.255 port 67 (xid=0x37c3b531) > DHCPREQUEST on em1 to 255.255.255.255 port 67 (xid=0x37c3b531) > DHCPACK from 192.168.1.1 (xid=0x37c3b531) > bound to 192.168.1.145 -- renewal in 19334 seconds. Reply at: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/1432599/comments/4 On 2015-01-09T23:03:58+00:00 Aleksandar wrote: Very strange, after restarting the router, network manager started to successfully start the em1 interface. Before restarting the router, only manual dhclient request was working. Can that be related to leasing IP? I couldn't find how to configure that in NetworkManager :( > After connection though I see the following in the log: > Jan 10 00:56:36 localhost NetworkManager[7383]: Activation (em1) > successful, device activated. > Jan 10 00:56:36 localhost dnsmasq[8458]: started, version 2.72 cachesize 400 > Jan 10 00:56:36 localhost dnsmasq[8458]: compile time options: IPv6 > GNU-getopt DBus no-i18n IDN DHCP DHCPv6 no-Lua TFTP no-conntrack ipset auth > DNSSEC loop-detect > Jan 10 00:56:36 localhost dnsmasq[8458]: using nameserver 192.168.1.1#53 > Jan 10 00:56:36 localhost dnsmasq[8458]: cleared cache > Jan 10 00:56:36 localhost dbus[1023]: [system] Activating via systemd: > service name='org.freedesktop.nm_dispatcher' > unit='dbus-org.freedesktop.nm-dispatcher.service' > Jan 10 00:56:36 localhost dbus[1023]: [system]
[Bug 1432599] Re: Network-manager tries to manage virbr0, which it should not
This affected me when I went from Xubuntu 15.10 to 16.04; the wired network icon would be shown whenever I wasn't connected to any actual networks, and adding the config tweak in #4 triages the issue for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1432599 Title: Network-manager tries to manage virbr0, which it should not To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1432599/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1432599] Re: Network-manager tries to manage virbr0, which it should not
For me this happened after upgrade from 15.04 to 15.10. Adding suggested fix to NetworkManager.conf solved the issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1432599 Title: Network-manager tries to manage virbr0, which it should not To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1432599/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1432599] Re: Network-manager tries to manage virbr0, which it should not
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: network-manager (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1432599 Title: Network-manager tries to manage virbr0, which it should not To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1432599/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1432599] Re: Network-manager tries to manage virbr0, which it should not
** Bug watch added: Red Hat Bugzilla #1166199 https://bugzilla.redhat.com/show_bug.cgi?id=1166199 ** Also affects: network-manager (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=1166199 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1432599 Title: Network-manager tries to manage virbr0, which it should not To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1432599/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1432599] Re: Network-manager tries to manage virbr0, which it should not
Taking a cue from https://bugzilla.redhat.com/show_bug.cgi?id=1166199 I worked around the issue by adding the following to my /etc/NetworkManager/NetworkManager.conf [keyfile] unmanaged-devices=interface-name:virbr0 Yet I imagine that the real solution is something more general. ** Changed in: network-manager (Ubuntu) Importance: Undecided = Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1432599 Title: Network-manager tries to manage virbr0, which it should not To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1432599/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1432599] Re: Network-manager tries to manage virbr0, which it should not
The /etc/NetworkManager/NetworkManager.conf [keyfile] unmanaged-devices=interface-name:virbr0 indeed does the trick. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1432599 Title: Network-manager tries to manage virbr0, which it should not To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1432599/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1432599] Re: Network-manager tries to manage virbr0, which it should not
Here is the feedback I got from the network-manager mailing list: On Thu, 2015-03-19 at 09:18 +0100, Franck Routier (perso) wrote: Hi list, I'm using Ubuntu and just upgraded to (still in development) Vivid. Now I see that network-manager handles my virbr0 bridge (libvirt), which it didn't before. NM will recognize and manage all network interfaces, but that does not mean that NM actually touches the interfaces. If the interface already has a configuration, NM simply assumes the existing configuration and waits for you to tell it to do something. That's a difference from older versions of NM (0.9.8 and earlier) where NM was mostly ignorant of existing configuration. We know that NM 0.9.10 still has a few edge cases where it touches interfaces and shouldn't, but almost all of those have already been fixed in NM 1.0 and later. Dan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1432599 Title: Network-manager tries to manage virbr0, which it should not To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1432599/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1432599] Re: Network-manager tries to manage virbr0, which it should not
Here is a bug report, related to the subject: https://bugzilla.gnome.org/show_bug.cgi?id=731014 Notice vboxnet0 also appears in nm-applet, but is shown as Unmanaged, unlike virbr0. ** Bug watch added: GNOME Bug Tracker #731014 https://bugzilla.gnome.org/show_bug.cgi?id=731014 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1432599 Title: Network-manager tries to manage virbr0, which it should not To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1432599/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1432599] Re: Network-manager tries to manage virbr0, which it should not
** Description changed: - Since a recent upgrade in vivid, nm is tryoing to manage virbr0. This + Since a recent upgrade in vivid, nm is trying to manage virbr0. This results in my main machine not getting a real IP address on eth0, and virtual machines not being able to use the network. This is probably related to https://bugzilla.redhat.com/show_bug.cgi?id=1166199 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu11 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 ApportVersion: 2.16.2-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 16 12:36:07 2015 IfupdownConfig: - # interfaces(5) file used by ifup(8) and ifdown(8) - auto lo - iface lo inet loopback + # interfaces(5) file used by ifup(8) and ifdown(8) + auto lo + iface lo inet loopback InstallationDate: Installed on 2014-12-13 (92 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) IpRoute: - default via 10.0.0.1 dev eth0 proto static metric 1024 - 10.0.0.0/24 dev eth0 proto kernel scope link src 10.0.0.75 - 192.168.111.0/24 dev wlan0 proto kernel scope link src 192.168.111.8 - 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 + default via 10.0.0.1 dev eth0 proto static metric 1024 + 10.0.0.0/24 dev eth0 proto kernel scope link src 10.0.0.75 + 192.168.111.0/24 dev wlan0 proto kernel scope link src 192.168.111.8 + 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 NetworkManager.state: - [main] - NetworkingEnabled=true - WirelessEnabled=true - WWANEnabled=true - WimaxEnabled=true + [main] + NetworkingEnabled=true + WirelessEnabled=true + WWANEnabled=true + WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) http_proxy: http://localhost:8118/ nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. no_proxy: localhost,127.0.0.0/8,::1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1432599 Title: Network-manager tries to manage virbr0, which it should not To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1432599/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
