Bug 1181477
| Summary: | wired connection because non-functional until I removed its lease file | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Kamil Páral <kparal> |
| Component: | NetworkManager | Assignee: | Dan Williams <dcbw> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 21 | CC: | amk, bugzilla, chepioq, dcbw, jklimes, psimerda |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | NetworkManager-0.9.10.1-1.4.20150115git.fc21 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-01-17 23:58:12 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Kamil Páral
2015-01-13 09:39:57 UTC
For reference, this is the lease file that gets created when I successfully connect in my work:
$ cat /var/lib/NetworkManager/dhclient-65bf8b50-fd35-4359-adff-24793c9b77f3-em1.lease
lease {
interface "em1";
fixed-address 10.34.28.207;
filename "/pxelinux.0";
option subnet-mask 255.255.254.0;
option dhcp-lease-time 86400;
option routers 10.34.29.254;
option dhcp-message-type 5;
option dhcp-server-identifier 10.34.255.7;
option domain-name-servers 10.34.255.7,10.34.255.6;
option ntp-servers 10.5.26.10,10.5.27.10,10.11.160.238,10.16.255.1;
option domain-name "brq.redhat.com englab.brq.redhat.com lab.eng.brq.redhat.com redhat.com";
renew 5 2013/02/22 19:49:06;
rebind 6 2013/02/23 05:27:17;
expire 6 2013/02/23 08:27:17;
}
default-duid "\000\001\000\001\034G\241\016\360\336\361\371\263\234";
lease {
interface "em1";
fixed-address 10.34.28.119;
filename "/pxelinux.0";
option subnet-mask 255.255.254.0;
option routers 10.34.29.254;
option dhcp-lease-time 3600;
option dhcp-message-type 5;
option domain-name-servers 10.38.5.26,10.11.5.19;
option dhcp-server-identifier 10.11.5.19;
option domain-search "brq.redhat.com.", "redhat.com.";
option ntp-servers 10.5.26.10,10.5.27.10;
option domain-name "brq.redhat.com";
renew 2 2015/01/13 09:49:38;
rebind 2 2015/01/13 10:18:06;
expire 2 2015/01/13 10:25:36;
}
We have a fix for this in master. It needs to be backported to 0.9.10 and pushed to Fedora. See upstream bug https://bugzilla.gnome.org/show_bug.cgi?id=739482. Note: First, I could not reproduce. I got DHCPNAK, but immediately after that dhclient initialized again and obtained a new lease successfully. I found that it was due to IPv6 method being Automatic. When I set IPv6 method to Ignore, the connection failed at once as you observe. So as a temporarily workaround, you could set the IPv6 method to Automatic instead of Ignore. *** Bug 1180398 has been marked as a duplicate of this bug. *** *** Bug 1181329 has been marked as a duplicate of this bug. *** *** Bug 1179985 has been marked as a duplicate of this bug. *** (In reply to Jirka Klimes from comment #2) > We have a fix for this in master. It needs to be backported to 0.9.10 and > pushed to Fedora. See upstream bug > https://bugzilla.gnome.org/show_bug.cgi?id=739482. > > Note: > First, I could not reproduce. I got DHCPNAK, but immediately after that > dhclient initialized again and obtained a new lease successfully. I found > that it was due to IPv6 method being Automatic. When I set IPv6 method to > Ignore, the connection failed at once as you observe. So as a temporarily > workaround, you could set the IPv6 method to Automatic instead of Ignore. I am the reporter for bug: 1180398 For me the workaround don't work. My IPv6 method is set to Automatic since I installed Fedora (21, 20, 19...), and I have this bug. I reported bug 1181329 that was marked and closed as a duplicate of this one. https://bugzilla.redhat.com/show_bug.cgi?id=1181329 The issue was reported for Version: 0.9.10.1 Release: 1.git20150105.fc21 Recently this was updated to Release: 1.2.20150109git.fc21 And it looks like the update has solved the issue. Sorry, but I install the 1.2.20150109git.fc21 release and that don't solve the issue. NetworkManager-0.9.10.1-1.4.20150115git.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/NetworkManager-0.9.10.1-1.4.20150115git.fc21 I install the update NetworkManager-0.9.10.1-1.4.20150115git.fc21 and that work for me. Thank. The update does *not* solve the DHCP problem, originally reported in bug #1179985. It still takes several attempts (systemctl restart NetworkManager) to get the DHCP-enabled wired interface into "connected" state. If somebody reports that it "works", then it's just because it's a random bug. Sometimes it works, sometimes not. The bug still exists. Package NetworkManager-0.9.10.1-1.4.20150115git.fc21: * should fix your issue, * was pushed to the Fedora 21 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing NetworkManager-0.9.10.1-1.4.20150115git.fc21' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-0802/NetworkManager-0.9.10.1-1.4.20150115git.fc21 then log in and leave karma (feedback). NetworkManager-0.9.10.1-1.4.20150115git.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report. (In reply to Andreas M. Kirchwitz from comment #11) > The update does *not* solve the DHCP problem, originally reported in bug > #1179985. It still takes several attempts (systemctl restart NetworkManager) > to get the DHCP-enabled wired interface into "connected" state. > > If somebody reports that it "works", then it's just because it's a random > bug. Sometimes it works, sometimes not. The bug still exists. If you can reproduce bug 1179985 with updated NetworkManager, can you please reopen it and attach details? Thanks. Sorry, my comment was badly timed and based on the previous update. Please accept my apologies for the confusion this has caused. After the brandnew update I've restarted the new "NetworkManager-0.9.10.1-1.4.20150115git.fc21" about a hundred times, and it worked fine 100%. Not a single failure. Looks great! Thanks a lot! |