Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem: When adding --nocore to the end of %packages in a kickstart you recieve an error


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


How reproducible: add %packages --nobase --nocore to a kickstart


Steps to Reproduce:
1. make a kickstart
2. add %packages --nobase --nocore
3. run the installer from kickstart

Actual results:
The --nocore option was introduced in version F21, but you are using kickstart syntax version DEVEL.

Expected results:
Kickstart running and completing 


Additional info: this was a bug that was found with 7.0 and was fixed with 7.1

Whenever you file a bug, please include what version of anaconda you are using and what version of installation media you are using.  Further, is this happening when you run through the installer, or are you using some tool with pykickstart to validate your kickstart file?  There's more data needed here before we can tell how to proceed.

Actually, I think this will fix it:

--- a/pykickstart/version.py
+++ b/pykickstart/version.py
@@ -73,9 +73,9 @@ F16 = 14000
 F17 = 15000
 F18 = 16000
 F19 = 17000
-RHEL7 = 17100
 F20 = 18000
 F21 = 19000
+RHEL7 = 19100
 F22 = 20000

Retested with pykickstart-1.99.66.6-1.el7, the installation started successfully with the following packages section:

%packages --nobase --nocore
%end

Moving to VERIFIED.

This bug should not need documentation - it was never present in a GA version.  It showed up due to the pykickstart rebase for 7.2, and then was fixed later on in 7.2 development.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-2285.html