Bug 471812
Summary: | crash booting with ks, expecting DHCP-provided kickstart config file name | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Alexandre Oliva <oliva> |
Component: | anaconda | Assignee: | David Cantrell <dcantrell> |
Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 10 | CC: | rmj |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-12-18 20:16:28 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: |
Description
Alexandre Oliva
2008-11-16 20:43:14 UTC
Seems this block didn't make it in the rewrite for the NetworkManager integration. Line 383 in loader/nfsinstall.c Working on a patch. This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle. Changing version to '10'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Booting from the netinst disk with 'ks' fails to bring up the network interface at first, and then, when I retry, it fails for good and crashes with a SIGSEGV. The /sbin/loader backtrace has: __strdup called by getHostPathandLogin called by getHostandPath called by getFileFromNfs called by getKickstartFile called by main. Before shutting the system down, it prints: nm-dispatcher.action: _nm_object_get_property: Error getting 'Ip4Config' fr /org/freedesktp/Hal/devices/net_<mm_aa_cc...>: Connection was disconnected before a reply was received. I tried with and without noipv6, to no avail. I don't have a dhcpv6 server, only dhcpv4. ks=nfs:server:/path/name manages to download the kickstart file after the initial failure, after you select retry, but then it doesn't seem to use the information in the kickstart file to start anaconda (maybe because I passed it askmethod). Fix will be in anaconda-11.4.1.59-1. |