Bug 242017

Summary:	Anaconda cannot be used for remote installation
Product:	[Fedora] Fedora	Reporter:	Tomas Pecina <tomas>
Component:	anaconda	Assignee:	David Cantrell <dcantrell>
Status:	CLOSED RAWHIDE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	low
Version:	7
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2007-08-23 18:33:29 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 Tomas Pecina 2007-06-01 10:15:35 UTC

Description of problem:

During remote installation, anaconda asks for manual network configuration
despite the fact that all the parameters are supplied in grub.conf. This
behavior was not observed in FC6, which installs smoothly with the same kernel
parameters.

Version-Release number of selected component (if applicable):

F7

How reproducible:

Steps to Reproduce:
1. Copy F7 vmlinuz&initrd.img to /boot.
2. Change /boot/grub/grub.conf for remote installation, supplying ip, netmask, etc.
3. Reboot.
4. Retest with FC6 vmlinuz&initrd.img files, which should work normally.
  
Actual results:

The remote system hangs up, prompting for keyboard entry.

Expected results:

The installation proceeds.

Additional info:

Comment 1 Tomas Pecina 2007-06-02 19:29:21 UTC

I found that IPV4 can be used for the former IP parameter, but it does not solve
the problem of the system hanging up showing the configuration screen and
waiting for keyboard entry, only fills in the IP address field.

Comment 2 David Cantrell 2007-08-23 18:33:29 UTC

This has been fixed in rawhide.  The stage 1 loader was always prompting for
network configuration information regardless of boot parameters.