Bug 192029

Summary:	@Base should be added to a kickstart by default.
Product:	Red Hat Satellite 5	Reporter:	John Wregglesworth <wregglej>
Component:	Provisioning	Assignee:	Kevin A. Smith <ksmith>
Status:	CLOSED WORKSFORME	QA Contact:	Beth Nackashi <bnackash>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	unspecified	CC:	rhn-bugs
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:	2006-05-16 22:28:11 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:
Bug Depends On:
Bug Blocks:	174413

Description John Wregglesworth 2006-05-16 22:21:35 UTC

Description of problem: When kickstarting FC5, anaconda dropped from an
automated install to a manual install when it got to the package selection step.
I took a look at the kickstart file that was generated for the profile and
noticed that @Base isn't included by default. I think it's the same kind of
issue I ran into with the network configuration line in bug# 192028, where the
new anaconda for FC5 doesn't seem to have defaults for that kind of stuff built
into it (that's pretty much speculation on my part).

How reproducible: Always


Steps to Reproduce:
1. Create a kickstart profile with only default values.
2. View the kickstart file that was generated for the profile.
3. See that @Base isn't included by default.
  
Actual results: @Base isn't included in the kickstart by default.


Expected results: @Base should be included by default.


Additional info: This can be worked around by adding @Base through the Software tab.

Comment 1 Mike McCune 2006-05-16 22:28:11 UTC

I tested this on webqa and on the latest rev of the java code on a satellite and
it does get @Base added by default to a new profile.