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:

Attempting to install centos 8 stream on some old hardware with a 3w-sas raid card in it. The plan was to use the driver disk feature to make the controller accessible using packages found here:

http://mirror.centos.org/centos/8-stream/kmods/x86_64/packages-main/Packages/k/

I copied the package to an internal web server and fed it to kickstart via the inst.dd kernel argument. Boot messages indicate the rpm being downloaded and processed, however once anaconda starts up it exits with an error that no storage can be found. Swapping to a shell and poking around confirms that the module is not loaded nor is the controller visible.

I flailed around a bit before digging into the rpm and noticed the module is compressed (eg, 3w-sas.ko.xz). I dug up the srpm and modified the spec file to not compress the module, then attempted a kickstart with the resulting rpm. The install succeeded.


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

anaconda 33.16.6.4

How reproducible:

Only tested the 3w-9xx and 3w-sas modules but the behavior was identical for both. Every kickstart attempt failed.

Steps to Reproduce:
1. Fetch a driver rpm from http://mirror.centos.org/centos/8-stream/kmods/x86_64/packages-main/Packages/k/
2. Configure a kickstart with inst.dd containing the url of your selected rpm
3. Run kickstart

Hello, could you please provide us logs from the installation? You can find them in /tmp/*.log. Ideally include all the files but minimal syslog is most important to us.

Also please boot the machine with rd.debug kernel boot parameter.

Created attachment 1846431 [details]
tarball of all logs produced by kickstart

Attaching all logs that were in /tmp when kickstart exited. 

If you need anything else, let me know.

Anaconda does not support loading compressed kernel modules at this time. This issue is request for enhancement.

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.