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:

The 'ksvalidator utility, when run using the RHEL6 version (e.g. 'ksvalidator -v RHEL6') throws an error when the 'key' kickstart command is present. This differs from the behavior of 'ksvalidator' in RHEL6, which does not error on this command.

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

For RHEL7:  pykickstart-1.99.43.17-1.el7.noarch
Comparing to RHEL6 version: pykickstart-1.74.20-1.el6.noarch

How reproducible:

Consistently.

Steps to Reproduce:
1. Create a RHEL6 kickstart file using the 'key' command in the kickstart header (e.g. 'key --skip')
2. Execute 'ksvalidator -v RHEL6 /path/to/kickstart-file.cfg'

Actual results:

An error is thrown, e.g.

The following problem occurred on line 8 of the kickstart file:

Unknown command: key


Expected results:

No errors are thrown (similar to the behavior in RHEL6).

Just needs a cherry-pick of 142c9b021f60ff00d63e855cd02dc951ee96c8f0.

Whoops, I should have run tests before pushing.  This actually needs a cherry-pick of c6252828993b9c34e4fac123196605c368fa0601.

Verified on pykickstart-1.99.66.9-1.el7.noarch, 'key' command is accepted for RHEL6.

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-2016-2184.html