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:


There are nearly 250 bugs against this component and it doesn't have an upstream test suite. Please provide one or at least a base framework for it so that QE can start adding tests.


Version-Release number of selected component (if applicable):
system-config-kickstart-2.9.2-1.el7.src.rpm

system-config-kickstart is largely deprecated, so it's unlikely that we will further revise it.  But I'm keeping the bug open for now.

(In reply to David Cantrell from comment #1)
> system-config-kickstart is largely deprecated, so it's unlikely that we will
> further revise it.  But I'm keeping the bug open for now.

Will it be removed then ? Will there be an alternative package ?

The immediate plan is to reuse anaconda code to provide the UI, since anaconda's just building kickstart files now.  However, I don't see getting around to doing tests for either it or the current UI given how low priority it's been lately.