Bug 465887
Summary: | NetworkManager crash when user changes ethernet device | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Gordon Messmer <gordon.messmer> |
Component: | anaconda | Assignee: | David Cantrell <dcantrell> |
Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | rawhide | CC: | anaconda-maint-list, dcantrell |
Target Milestone: | --- | Keywords: | Reopened |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | NEEDSRETESTING | ||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-11-07 23:24:52 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 469046 |
Description
Gordon Messmer
2008-10-06 23:02:21 UTC
This is fixed in rawhide now, will be included in anaconda-11.4.1.46-1. Thank you for the report. Anaconda still crashes in snapshot 3, but in a different way. The problem can be reproduced the same as before: select the wrong interface and then the correct one after it times out. I notice that when I select the wrong interface, I'm asked for IP settings. After it times out and I select the second interface, anaconda doesn't ask for the desired IP settings. After it attempts DHCP on the correct interface, anaconda crashes. I can't see a lot of the error message, but I see this near the end: Method "Get" with signature "ss" on interface "org.freedesktop.DBus.Properties" doesn't exist. The problem here is that when the interface could not be brought up, we were not blanking out the configuration methods internally. So when you'd select a new interface, loader would skip right past the configuration screen for the TCP/IP settings. This patch should fix things up: diff --git a/loader/net.c b/loader/net.c index 846712f..62dc236 100644 --- a/loader/net.c +++ b/loader/net.c @@ -453,6 +453,8 @@ int readNetConfig(char * device, iface_t * iface, if (err) { logMessage(ERROR, "failed to write %s data for %s (%d)", SYSCONFIG_PATH, iface->device, err); + iface->ipv4method = IPV4_UNUSED_METHOD; + iface->ipv6method = IPV6_UNUSED_METHOD; return LOADER_BACK; } @@ -463,6 +465,8 @@ int readNetConfig(char * device, iface_t * iface, newtWinMessage(_("Network Error"), _("Retry"), _("There was an error configuring your network " "interface.")); + iface->ipv4method = IPV4_UNUSED_METHOD; + iface->ipv6method = IPV6_UNUSED_METHOD; return LOADER_BACK; } } BTW, I'll move the bug to MODIFIED once I commit the change to anaconda. Patch committed to anaconda, will be in the anaconda-11.4.1.56-1 build. That anaconda will be in rawhide 20081108 or later. Please re-test it. I can do that if you can point me at documentation on updating the installation image. You would just launch the installer from rawhide (the <arch>/os/images/boot.iso file) and repeat what you did the first time to get it to crash. I spun up a tree with this anaconda build and confirmed that this bug is fixed. Closing. |