Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
For bugs related to Red Hat Enterprise Linux 5 product line. The current stable release is 5.10. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 280101

Summary: generated anaconda-ks.cfg %packages differs from %packages in kickstart
Product: Red Hat Enterprise Linux 5 Reporter: Alexander Todorov <atodorov>
Component: anacondaAssignee: Martin Sivák <msivak>
Status: CLOSED ERRATA QA Contact: Milan Zázrivec <mzazrivec>
Severity: low Docs Contact:
Priority: medium    
Version: 5.2CC: amm
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: RHBA-2008-0397 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-05-21 15:31:43 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:

Description Alexander Todorov 2007-09-06 07:46:03 UTC 
Description of problem:
Using ks.cfg containing
------------------
%packages
@Everything
------------------
or
------------------
%packages
*
------------------

produces anaconda-ks.cfg containing @core, @base and some other packages,
which doesn't recreate the same system. Number of installed packages is 2098.

Performing manual install and customizing the packages selection in GUI works as
expected. Right clicking with the mouse and selecting "All
optional packages" for every group leads to anaconda-ks.cfg file that recreates
the same system when used for subsequent install.

All installs are with latest RHEL5.1-Server-20070905.nightly tree, not using
installation key (Server repo only).

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

How reproducible:
Always

Steps to Reproduce:
1. Use a kickstart file for installation containing @Everything(*) in the
packages section.
2. Complete the install and get the generated anaconda-ks.cfg
3. Both kickstart files should contain the same packages section.
4. Both kickstart files should lead to the same set of installed packages.
(Re-install with anaconda-ks.cfg to retest).
  
Actual results:
anaconda-ks.cfg generated when using @Everything:
https://bugzilla.redhat.com/attachment.cgi?id=187291

Expected results:
generated anaconda-ks.cfg contains the same packages section as used kickstart
during installation.

Additional info:
Manual selection of packages seem to work correctly. See Bug #227383
Comment 1 Chris Lumens 2007-09-06 13:57:05 UTC 
Created attachment 188781 [details]
use input %packages section for anaconda-ks.cfg

This may need a little tweaking because pykickstart in RHEL5 is significantly
different from the one in rawhide.
Comment 2 Chris Lumens 2007-09-11 20:03:21 UTC 
*** Bug 235454 has been marked as a duplicate of this bug. ***
Comment 4 RHEL Program Management 2007-10-16 03:42:06 UTC 
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release.  Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products.  This request is not yet committed for inclusion in an Update
release.
Comment 6 Milan Zázrivec 2008-02-06 15:31:03 UTC 
Verified with RHEL5.2-{Client,Server}-20080206.nightly / anaconda-11.1.2.96-1
Comment 8 errata-xmlrpc 2008-05-21 15:31:43 UTC 
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2008-0397.html