Bug 214990 - Anaconda doesn't honor "key" keyword in kickstart file
Summary: Anaconda doesn't honor "key" keyword in kickstart file
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: anaconda   
(Show other bugs)
Version: 5.0
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: Anaconda Maintenance Team
QA Contact:
URL: https://www.redhat.com/archives/rhelv...
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-11-10 14:49 UTC by Jason Edgecombe
Modified: 2007-11-30 22:07 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-11-10 15:26:19 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
Sample kickstart file (1.44 KB, text/plain)
2006-11-10 14:49 UTC, Jason Edgecombe
no flags Details

Description Jason Edgecombe 2006-11-10 14:49:29 UTC
Description of problem:
When installing RHEL5b1 using kickstart, certain packages like gcc & make will
not install even if specified in the %packages section.

After consulting the rhel5b1 redhat email list, I have tried inserting the "key"
directive in the file file in order to choose the type of install (Client,
Workstation, Server, ...). The key is the same as the registration code (i.e. DW)

When using the "key" directive, the installer gives an error about "key" is not
a valid command.

See email discussion at
https://www.redhat.com/archives/rhelv5-beta-list/2006-November/msg00006.html

Version-Release number of selected component (if applicable):
Anaconda version  11.1.0.77-9

How reproducible:
always

Steps to Reproduce:
1. Copy RHEL5b1 ISO contents to a shared directory on an nfs server (I didn't
run genhdlist)
2. run a kickstart install using the attached file which includes the "key"
directive
3.
  
Actual results:
Using the Key directive produces an error. Not using the key directive excludes
useful packages like gcc and make which cause errors when specified in the
kickstart file

Expected results:
When I specify the gcc and make packages in kickstart, it should install gcc and
make.

Additional info:
Mailing list thread:
https://www.redhat.com/archives/rhelv5-beta-list/2006-November/msg00006.html

When doing a manual install, the key directive is not saved in the
/root/anaconda-ks.cfg file.

Comment 1 Jason Edgecombe 2006-11-10 14:49:29 UTC
Created attachment 140889 [details]
Sample kickstart file

Comment 2 Jeremy Katz 2006-11-10 15:26:19 UTC
Support for the key directive wasn't added until post-beta1


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