Bug 192029 - @Base should be added to a kickstart by default.
@Base should be added to a kickstart by default.
Status: CLOSED WORKSFORME
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Provisioning (Show other bugs)
unspecified
All Linux
medium Severity medium
: ---
: ---
Assigned To: Kevin A. Smith
Beth Nackashi
:
Depends On:
Blocks: rhn410-kickstart
  Show dependency treegraph
 
Reported: 2006-05-16 18:21 EDT by John Wregglesworth
Modified: 2007-10-29 21:57 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-05-16 18:28:11 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description John Wregglesworth 2006-05-16 18:21:35 EDT
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 18:28:11 EDT
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.

Note You need to log in before you can comment on or make changes to this bug.