Bug 153216 - Incosistence between installation image and system-config-kickstart
Incosistence between installation image and system-config-kickstart
Status: CLOSED DUPLICATE of bug 143094
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: system-config-kickstart (Show other bugs)
i386 Linux
medium Severity low
: ---
: ---
Assigned To: Chris Lumens
Depends On:
  Show dependency treegraph
Reported: 2005-04-03 04:20 EDT by Dan Fruehauf
Modified: 2007-11-30 17:07 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-04-04 04:10:39 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Dan Fruehauf 2005-04-03 04:20:09 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050302 Firefox/1.0.1 Fedora/1.0.1-1.3.2

Description of problem:
There are some inconsistencies between RHEL4 out of the box and system-config-kickstart.
One noticable inconsistence is the Kernel Development meta package which shows on system-config-kickstart but doesnt appear in comps.xml of RHEL4.
This is one inconsistency, which causes some discomfort, but i'm pretty sure if i'll find the time to dig it, more will follow.
The incorrect package selection is in the file /usr/share/system-config-kickstart/RHELPackageGroupList.py

It is a minor bug, but as i said, there might be more inconsistencies.

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

How reproducible:

Steps to Reproduce:
1. Open system-config-kickstart and choose the Kernel Development package
2. Save your arbitary kickstart file
3. Run a kickstart installation and notice that you cant install the Kernel Development package

Actual Results:  Installer prompts for user input

Expected Results:  The installer should have ran without asking anything

Additional info:

There is a very easy workaround, which is just not to check that box, but i had already enough confused and inexperienced users who wasted their time on this minor bug.
Comment 1 Jay Turner 2005-04-04 04:10:39 EDT

*** This bug has been marked as a duplicate of 143094 ***

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