Hide Forgot
All kmod packages provided as DUP in RHEL-8 need fixing because symvers.gz has been moved. kmod-redhat-bnxt_en.x86_64 1.10.0_dup8.1-2.el8_1 kmod-redhat-btusb.x86_64 0.8_4.18.0_80.23_dup8.0-4.el8_0 kmod-redhat-btusb-firmware.x86_64 21.10.0.6_dup8.0-4.el8_0 kmod-redhat-ice.x86_64 0.8.2_k_dup8.2-1.el8_2 kmod-redhat-ice-firmware.x86_64 1.3.4.0_dup8.2-1.el8_2 kmod-redhat-ionic.x86_64 4.18.0.210_dup8.2-2.el8_2 kmod-redhat-iwlwifi.x86_64 4.18.0_107_dup8.0-5.el8_0 kmod-redhat-iwlwifi-devel.x86_64 4.18.0_107_dup8.0-5.el8_0 kmod-redhat-iwlwifi-firmware.x86_64 20190516_dup8.0-5.el8_0 kmod-redhat-mlx5_core.x86_64 5.0_0_dup8.2-2.el8_2 kmod-redhat-mlx5_core-devel.x86_64 5.0_0_dup8.2-2.el8_2 In RHEL-8, symvers.gz was moved from /boot to /lib/modules as shown in the kernel changelog: * Mon Aug 13 2018 Herton R. Krzesinski <herton> [4.18.0-1.el8] - [rpmspec] Copy symvers.gz to /lib/modules (Eugene Syromiatnikov) [1609695] The %posttrans section of the kernel spec file has the following: # The same check as in weak-modules: we assume that the kernel present # if the symvers file exists. if [ -e "/boot/symvers-$k.gz" ]; then /usr/bin/dracut -f "$tmp_initramfs" "$k" || exit 1 cmp -s "$tmp_initramfs" "$dst_initramfs" if [ "$?" = 1 ]; then mv "$tmp_initramfs" "$dst_initramfs" else rm -f "$tmp_initramfs" fi fi This issue was originally reported by an ELRepo user: https://elrepo.org/bugs/view.php?id=1060 As shown in our bug tracker, we (ELRepo) propose to fix this by changing the line: if [ -e "/boot/symvers-$k.gz" ]; then to if [ -e "$k_dir/symvers.gz" ]; then
Oops, %posttrans section of the kmod spec, not kernel spec.
Summary: the issue is fixed in the ddiskit script used to generate DUPs, an additional testing step is to be added to check that the issue won't re-appear in future DUPs. The issue in the following released RHEL 8 DUPs has been handled as follows: * kmod-redhat-btusb-0.8_4.18.0_80.23_dup8.0-4.el8_0: not updated, the change didn't meet the criteria to push an update to RHEL 8.0; * kmod-redhat-iwlwifi-4.18.0_107_dup8.0-5.el8_0: not updated, the change didn't meet the criteria to push an update to RHEL 8.0; * kmod-redhat-bnxt_en-1.10.0_dup8.1-2.el8_1: not updated, the change didn't meet the criteria to push an update to RHEL 8.1; * kmod-redhat-ice-0.8.2_k_dup8.2-1.el8_2: an updated kmod-redhat-ice-0.8.2_k_dup8.2-2.el8_2[1] has been released; * kmod-redhat-ionic-4.18.0.210_dup8.2-2.el8_2: an updated kmod-redhat-ionic-4.18.0.210_dup8.2-3.el8_2[2] has been released; * kmod-redhat-mlx5_core-5.0_0_dup8.2-2.el8_2: an updated kmod-redhat-mlx5_core-5.0_0_dup8.2-3.el8_2[3] has been released; * kmod-redhat-ena-2.1.0K_dup8.3-1.el8_3: an update that includes the fix is planned to be released in the future; * kmod-redhat-oracleasm-2.0.8-1.el8_3: not updated, the kmod is not used during early boot; * kmod-redhat-mpt3sas-35.101.00.00_dup8.3-1.el8_3: the package has been released with the %posttrans script fix already present. ISOs haven't been updated as those are primarily used during installation where the issue is not manifested. A KB article[4] has been prepared to cover the issue, provide a workaround, and point to the updates where possible (it seems to be not yet published, though). I am closing the issue as fixed; if you think that any further action is needed, feel free to re-open it. [1] https://access.redhat.com/errata/RHBA-2021:0212 [2] https://access.redhat.com/errata/RHBA-2021:0211 [3] https://access.redhat.com/errata/RHBA-2021:0213 [4] https://access.redhat.com/solutions/5681371
Thanks for the update. I do not have permissions to access the KB article you link (https://access.redhat.com/solutions/5681371) even when logged in with RH account. Error is: Access Denied You do not have permission to access the page you requested. Please could you fix the permissions.
(In reply to Phil Perry from comment #5) > Thanks for the update. > > I do not have permissions to access the KB article you link > (https://access.redhat.com/solutions/5681371) even when logged in with RH > account. Error is: > > > Access Denied > > You do not have permission to access the page you requested. > > > Please could you fix the permissions. It is published now, my apologies for the delay.