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:
RHEL 8 does not use a kickstart (ks.cfg) located on a drive labeled OEMDRV

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

How reproducible:
Everytime

Steps to Reproduce:
1.Create a drive labeled OEMDRV and place a valid kickstart on it (ks.cfg)
2. Boot the installation with the OEMDRV connected
3.

Actual results:
Manual installation, no ks.cfg fouund in the installation environment

Expected results:
Anaconda should automatically find ks.cfg in drives labeled OEMDRV and apply it to the installation.

Additional info:
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html-single/performing_an_advanced_rhel_installation/index#making-a-kickstart-file-available-on-a-local-volume-for-automatic-loading_making-kickstart-files-available-to-the-installation-program

This could be a duplicate of bug 1770969. Could you please add "rd.debug" on the kernel command line when starting the installation and see if it helps as a workaround?

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