Bug 694168

Summary:	No option to manually configure interface for network on build
Product:	Red Hat Enterprise Linux 6	Reporter:	Leam <leamhall>
Component:	anaconda	Assignee:	Anaconda Maintenance Team <anaconda-maint-list>
Status:	CLOSED NOTABUG	QA Contact:	Release Test Team <release-test-team>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.1	CC:	borgan, notting
Target Milestone:	rc
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-04-06 22:46:59 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Leam 2011-04-06 16:37:08 UTC

Description of problem:

When buliding a server with a Kickstart file and the RPMs on a different server, the boot.iso only allows NetworkManager to try DHCP to configure the interface. There's no option to manually configure the interface.

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

How reproducible:

Try to boot and point to an external Kickstart file source
  
Actual results:

NetworkManager tries to configure the interface via DHCP.

Expected results:

Option to manually configure interface with IP and Network information.

Additional info:

This is kind of a show stopper for installing 6.1.

Comment 2 RHEL Program Management 2011-04-06 16:44:26 UTC

Since RHEL 6.1 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.

Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.

Comment 3 Brock Organ 2011-04-06 20:22:17 UTC

(In reply to comment #3)
> Description of problem:
> 
> When buliding a server with a Kickstart file and the RPMs on a different
> server, the boot.iso only allows NetworkManager to try DHCP to configure the
> interface. There's no option to manually configure the interface.

Hi Leam, 

To make sure I am understanding the problem properly, are you only seeing the bad behavior when using distinct servers for the kickstart file versus the product repos?  (ie kernel parameters something like this:

linux ks=http://serverA/ks.cfg repo=http://serverB/path/to/repos

Or does your kernel command line/ks.cfg data look differently ...?

Best Regards,

Brock

Comment 4 Brian Lane 2011-04-06 22:46:59 UTC

Pass 'asknetwork' on the kernel command line.

Comment 5 Leam 2011-04-08 14:46:21 UTC

Interesting...so far that works. However, it also seems to cause an issue if the Kickstart file as a network configuration line. For example, 

network --device eth0 --bootproto static --ip 192.168.1.250 --netmask 255.255.255.0 --hostname mynewserver

Even taking out the --device, --ip, and --netmask stuff it fails. Which means we'll have to manually set the hostname configuration info once the server is built.