View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001429 | channel: elrepo/el9 | kmod-megaraid_sas | public | 2024-02-14 03:54 | 2024-02-14 04:56 |
| Reporter | redbaron_4 | Assigned To | pperry | ||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | resolved | Resolution | no change required | ||
| Summary | 0001429: Cannot use the 9.3 DUD for fresh install of 9.3 Rocky Linux using PXE boot | ||||
| Description | Hi, I have a PXE setup where appropriate kmod-megaraid-sas DUDs are automatically added to kickstart files (using driverdisk option) based on Rocky 9 version to be installed. I downloaded the hosted DUD for 9_3 (dd-megaraid_sas-07.725.01.00-1.el9_3.elrepo.iso) for use in installing Rocky9.3. The installation is however failing at "Package Install" step of PXE with an error like nothing provides kernel(__dynamic_dev_dbg) needed by kmod-megaraid-sas-07.725 and a bunch of similar errors My suspicion is that there is a new megaraid-sas RPM in elrepo (kmod-megaraid_sas-07.725.01.00-3.el9_3.rpm) which is attempted for update by package installation process. However, the kernel that ships with PXE boot image of Rocky-9.3 is 5.14.362-8.1 which is incompatible with what is required for that RPM (It requires -18.1). As a workaround, I can install Rocky-9.2 and then do a dnf upgrade to get a working 9.3 instance but I was wondering if there is some way by which I can get PXE install working correctly. Apologies as this is probably not directly an ElRepo issue | ||||
| Tags | dud, kernel, rocky | ||||
|
|
Hi, Unfortunately I have little to no experience with PXE / kickstart installations so am unsure I will be able to help you. From the error you are seeing, it does sound like your installation maybe trying to pull in the latest updated kmod package but the build cannot find the updated kernel it was built against. There have been a couple of kernel updates in el9.3 that have broken compatibility with kmod-megaraid_sas. Consequently: Version 07.725.01.00-1 will only work with kernel-5.14.0-362.8.1.el9_3. This is the version in the DUD as is designed for use with the RHEL 9.3 release media Version 07.725.01.00-2 will only work with kernel-5.14.0-362.13.1.el9_3 Version 07.725.01.00-3 will only work with kernel-5.14.0-362.18.1.el9_3 The package Requires will automatically match to the correct kernel providing the required kernel symbols, but will lead to the errors you note if the matching kernel is not available. If your installation is attempting to update to kmod-megaraid_sas-07.725.01.00-3, and the corresponding kernel-5.14.0-362.18.1.el9_3 is not available, you will see the errors you describe. I'm not sure if a pxe / kickstart installation further complicates this. Can you remove the availability (exclude maybe) of the updated kmod-megaraid_sas-07.725.01.00-3 packages (release -2 and -3) during the installation as a potential workaround? |
|
|
Thanks for the input! This kind of confirms what I am seeing regarding package versions and kernel numbers. I can maybe disable the elrepo during fresh install but that would complicate matters as latest kernel (-18.1) will be pulled from Rocky9 repos but kmod-megaraid_sas would be kmod-megaraid_sas-07.725.01.00-1 (packaged as DUD) and not compatible with that kernel. My suspicion is that dnf when doing a fresh install works somewhat differently from `dnf upgrade` done using command line as the latter can correctly resolve dependencies etc. Please feel free to close this issue (I am not sure how I can do it). |
|
|
Yes, we have seen complications previously when doing kickstart installs. If you disable elrepo during the install, and the installation pulls in the updated kernel, that should be fine (you shouldn't see any dnf errors) as long as you do not try to reboot to that updated kernel. If as part of the installation process, the system attempts to restart the new kernel will not be able to find the megaraid SAS device (as the updated driver for that kernel is missing). Can you also exclude kernel updates in your installation process, so you are effectively performing a vanilla installation of kmod-megaraid_sas-07.725.01.00-1 against kernel-5.14.0-362.8.1.el9_3 Once installation has completed, you should be able to perform a regular dnf update as normal. Marking as no change required as I do not think there is anything we can do in this case. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2024-02-14 03:54 | redbaron_4 | New Issue | |
| 2024-02-14 03:54 | redbaron_4 | Status | new => assigned |
| 2024-02-14 03:54 | redbaron_4 | Assigned To | => pperry |
| 2024-02-14 03:54 | redbaron_4 | Tag Attached: dud | |
| 2024-02-14 03:54 | redbaron_4 | Tag Attached: kernel | |
| 2024-02-14 03:54 | redbaron_4 | Tag Attached: rocky | |
| 2024-02-14 04:30 | pperry | Note Added: 0009565 | |
| 2024-02-14 04:39 | redbaron_4 | Note Added: 0009566 | |
| 2024-02-14 04:55 | pperry | Note Added: 0009567 | |
| 2024-02-14 04:56 | pperry | Status | assigned => resolved |
| 2024-02-14 04:56 | pperry | Resolution | open => no change required |
| 2024-02-14 04:56 | pperry | Note Edited: 0009567 |
