Description of problem: Thanks for making dkms available for epel8. It seems to have the same problem as in https://bugzilla.redhat.com/show_bug.cgi?id=1709940, in that modules are not being rebuilt when a new kernel is installed, but only at the next reboot. This can result in quite slow reboots (eg for openafs). Version-Release number of selected component (if applicable): dkms-2.7.1-2.el8.noarch How reproducible: Always Steps to Reproduce: 1. dnf install dkms 2. install something that uses dkms, eg the nvidia driver, or openafs 3. install a new kernel Actual results: Module for new kernel is not built at install time, but only on reboot. Expected results: Module for new kernel is built right away through /etc/kernel/postinst.d/dkms Additional info: grubby in rhel8 does not include /sbin/new-kernel-pkg, so /etc/kernel/postinst.d/dkms isn't run. Instead, there is /usr/lib/kernel/install.d/ See https://bugzilla.redhat.com/show_bug.cgi?id=1709940 for more info. In Fedora this was fixed in grubby, through the addition of a /lib/kernel/install.d/95-kernel-hooks.install script that runs the /etc/kernel/postinst.d/ scripts
Looks like there is a (slightly different) upstream dkms patch for this at https://github.com/dell/dkms/pull/118
Seems to be fixed in dkms-2.8.1-4.20200214git5ca628c.el8.noarch, which now includes a /usr/lib/kernel/install.d/40-dkms.install
FEDORA-2020-11149b8db4 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-11149b8db4
FEDORA-EPEL-2020-86a69a0d33 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-86a69a0d33
FEDORA-EPEL-2020-2a4c2c399e has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-2a4c2c399e
FEDORA-2020-bc1ecad001 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-bc1ecad001
FEDORA-2020-bc1ecad001 has been pushed to the Fedora 31 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-bc1ecad001` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-bc1ecad001 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-11149b8db4 has been pushed to the Fedora 32 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-11149b8db4` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-11149b8db4 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2020-2a4c2c399e has been pushed to the Fedora EPEL 8 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-2a4c2c399e See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2020-86a69a0d33 has been pushed to the Fedora EPEL 7 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-86a69a0d33 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-bc1ecad001 has been pushed to the Fedora 31 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2020-11149b8db4 has been pushed to the Fedora 32 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-EPEL-2020-2a4c2c399e has been pushed to the Fedora EPEL 8 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-EPEL-2020-86a69a0d33 has been pushed to the Fedora EPEL 7 stable repository. If problem still persists, please make note of it in this bug report.