[Bug 1075232] New: 0.9.0 Adds virtual interface, NetworkManager attempts to assign dhcp address to it
https://bugzilla.redhat.com/show_bug.cgi?id=1075232
Bug ID: 1075232 Summary: 0.9.0 Adds virtual interface, NetworkManager attempts to assign dhcp address to it Product: Fedora Version: 20 Component: docker-io Assignee: lsm5@redhat.com Reporter: admiller@redhat.com QA Contact: extras-qa@fedoraproject.org CC: admiller@redhat.com, golang@lists.fedoraproject.org, lsm5@redhat.com, mattdm@redhat.com, mgoldman@redhat.com, skottler@redhat.com, vbatts@redhat.com
Created attachment 873221 --> https://bugzilla.redhat.com/attachment.cgi?id=873221&action=edit snippet from /var/log/messages for my laptop around the virtual interface events
Description of problem: When you install docker-io-0.9.0 on Fedora 20, it creates a new virtual interface
13: vethf3e3: <BROADCAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master docker0 state UP group default qlen 1000 link/ether 1a:9c:40:61:1e:8b brd ff:ff:ff:ff:ff:ff inet6 fe80::189c:40ff:fe61:1e8b/64 scope link valid_lft forever preferred_lft forever
Something (I'm thinking dbus or udev) causes NetworkManager to launch dhclient for the new interface, and if you're running with a Desktop Environment this causes a visual change to the NM applet which can be confusing. It doesn't ever do anything, NM eventually times out and gives up and this doesn't appear to impact docker's functionality at all (or at least not yet in my tests have I found an issue, networking works fine).
Version-Release number of selected component (if applicable): docker-io-0.9.0-2.fc20.x86_64
How reproducible: Always
Steps to Reproduce: 1. yum install docker-io #on a machine with a GUI/DE up and running with NetworkManager
Actual results: NetworkManager attempts to get a dhcp lease on the new virtual interface.
Expected results: NetworkManager probably shouldn't attempt to get a dhcp lease on the new virtual interface, this seems odd.
Additional info:
https://bugzilla.redhat.com/show_bug.cgi?id=1075232
Daniel Walsh dwalsh@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |dcbw@redhat.com Component|docker-io |NetworkManager Assignee|lsm5@redhat.com |dcbw@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1075232
Dan Williams dcbw@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(admiller@redhat.c | |om)
--- Comment #1 from Dan Williams dcbw@redhat.com --- There's an NM config option for this which you can add to /etc/NetworkManager/NetworkManager.conf:
[main] no-auto-default=*
Or possibly better yet, 'yum install NetworkManager-config-server'. Do either of those fix the problem?
https://bugzilla.redhat.com/show_bug.cgi?id=1075232
Vaidas Jablonskis jablonskis@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jablonskis@gmail.com
--- Comment #2 from Vaidas Jablonskis jablonskis@gmail.com --- Neither of those help unfortunately.
https://bugzilla.redhat.com/show_bug.cgi?id=1075232
Jirka Klimes jklimes@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jklimes@redhat.com
--- Comment #3 from Jirka Klimes jklimes@redhat.com --- The original logs show that the default connection is created: Added default wired connection 'Wired connection 1' for /virtual/device/placeholder/3
That is controlled by the [main] no-auto-default=*
Would anyone seeing the problem, try with newest NM and grab relevant logs? Also, 'nmcli con dev' output would be useful.
https://bugzilla.redhat.com/show_bug.cgi?id=1075232
Jyri-Petteri Paloposki jyri-petteri.paloposki@iki.fi changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jyri-petteri.paloposki@iki. | |fi
--- Comment #4 from Jyri-Petteri Paloposki jyri-petteri.paloposki@iki.fi --- This is probably about this upstream bug: https://bugzilla.gnome.org/show_bug.cgi?id=731014 There seems to be a fix already, would it be possible to pull the fix to the Fedora package quickly? This is quite an annoying problem for VirtualBox / Docker / ... users.
I think that bug 1122525 is also about the same problem.
https://bugzilla.redhat.com/show_bug.cgi?id=1075232
--- Comment #5 from Fedora End Of Life endoflife@fedoraproject.org --- 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.
https://bugzilla.redhat.com/show_bug.cgi?id=1075232
--- Comment #6 from Jens Petersen petersen@redhat.com --- I think this is also true for F21, no?
https://bugzilla.redhat.com/show_bug.cgi?id=1075232
--- Comment #7 from Vaidas Jablonskis jablonskis@gmail.com --- (In reply to Jens Petersen from comment #6)
I think this is also true for F21, no?
Correct.
https://bugzilla.redhat.com/show_bug.cgi?id=1075232
Fedora End Of Life endoflife@fedoraproject.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CLOSED Resolution|--- |EOL Last Closed| |2015-06-29 15:24:58
--- Comment #8 from Fedora End Of Life endoflife@fedoraproject.org --- 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.
golang@lists.fedoraproject.org
-
Red Hat Bugzilla