Bug 743307

Summary:	kickstart firstboot --reconfig doesn't do network config
Product:	Red Hat Enterprise Linux 6	Reporter:	Mark J Strawcutter <mjstraw>
Component:	doc-Installation_Guide	Assignee:	Jack Reed <jreed>
Status:	CLOSED CURRENTRELEASE	QA Contact:	ecs-bugs
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.1	CC:	dayleparker, jreed, jskeoch, mgracik, pbokoc
Target Milestone:	rc	Keywords:	Documentation
Target Release:	---
Hardware:	x86_64
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-06-21 23:56:20 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Bug Depends On:
Bug Blocks:	756082

Description Mark J Strawcutter 2011-10-04 14:47:09 UTC

Description of problem:

kickstart install, ks.cfg specifies:

firstboot --reconfig

documentation says:

"This mode enables the language, mouse, keyboard, root password, security level, time zone, and networking configuration options in addition to the default ones."

however, no networking configuration options are presented 

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


How reproducible:

kickstart install with specified command in ks.cfg

Steps to Reproduce:
1. include specified command in ks.cfg
2. perform kickstart install
3.
  
Actual results:

firstboot runs, no netwworking configuration options are presented

Expected results:

firstboot presents networking configuration options along with the rest

Additional info:

Comment 2 Martin Gracik 2011-10-04 14:57:56 UTC

The network module was removed from firstboot, so this needs to be changed in the documentation.

Comment 3 Jack Reed 2011-12-09 00:17:01 UTC

Thanks Mark and Martin.

I've deleted 'network' from the list of configuration options in that paragraph. The change will be available in the 6.3 version of the guide.

Comment 7 Dayle Parker 2012-06-21 23:56:20 UTC

This bug is now fixed and available as part of the Red Hat Enterprise Linux 6.3 release on http://docs.redhat.com/.

Setting to CLOSED > CURRENTRELEASE.