Bug 465314

Summary:	Booting with "ks=http..." fails when attempting to activate network in stage#1
Product:	[Fedora] Fedora	Reporter:	James Laska <jlaska>
Component:	anaconda	Assignee:	Anaconda Maintenance Team <anaconda-maint-list>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	rawhide	CC:	anaconda-maint-list, dcantrell, hdegoede, jturner
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-10-02 18:49:53 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 James Laska 2008-10-02 18:21:00 UTC

Description of problem:
PXE Boot while providing static IP configuration prompts for networking details
in stage#1.

Version-Release number of selected component (if applicable):
 * rawhide=20081002/x86_64
 * anaconda-11.4.1.42-1

How reproducible:
100%

Steps to Reproduce:
1. PXE boot the noted rawhide tree
2. Add boot arguments: ks=http://jlaska.fedorapeople.org/ks.cfg
3. When prompted, enter lang=en and keymap=us
4. Select URL install method
5. Use defaults (dhcp and autodiscovery), select OK

Actual results:
Prompted for networking details again.  It appears a dialog popup flashes really quickly (likely a "Activating eth0 using NetworkManager ..." or similar).

Expected results:
DHCP should work.

Additional info:

tty3 states - FAILED to start NetworkManager (6) - see http://jlaska.fedorapeople.org/ks=http.png

Using a shell.gz to get a shell in loader on tty1, I see some failure messages in /tmp/anaconda.log 

http://jlaska.fedorapeople.org/ks=http-tty1.png

Please advise if there is any additional diagnostic information you need.

Comment 1 Hans de Goede 2008-10-02 18:49:53 UTC


*** This bug has been marked as a duplicate of bug 462083 ***