Bug 1704698

Same on Fedora 30.

Changing to component 'kernel' because 'dkms' seems to have just one person on CC list.

The DKMS scripts are maintained by a different team. Please keep it on there for now unless you identify a specific fix required for the kernel.

Also note that module signing was broken for a bit with the 5.0 series. Please test on 5.0.10-200 for F29.

Kernel version 5.0.10-200 is required to be able to load the self-signed module at all (https://bugzilla.redhat.com/show_bug.cgi?id=1701096)-

But my problem is related to the way, the POST_BUILD script is invoked.

This works:
sudo dkms install veeamsnap/3.0.1.1046 -k 5.0.10-200.fc29.x86_64

This is failing:
sudo dkms remove veeamsnap/3.0.1.1046 -k 5.0.10-200.fc29.x86_64
sudo dkms autoinstall

When using autoinstall, the variables ($module, $module_version, $kernelver, $arch) are not substituted when invoking the POST_BUILD script.

Background information:
The issue in the first post is from somebody else. I stumbled over it when I was troubleshooting the same issue on my side.
But it seems like nobody cares about in that DELL issue tracker as this is clearly not a hardware vendor thing.

My context is this one:
https://forums.veeam.com/veeam-agent-for-linux-f41/uefi-secure-boot-on-fedora-t59054.html

Seems like dkms autoinstall isn't called at all any more starting with kernel 5.0.10 or 5.0.11.

I have noticed that dkms has trouble to build modules for newly installed kernels during system boot (i.e. by dkms service). The module itself builds fine but depmod fails:
depmod: FATAL: renameat(/lib/modules/5.0.14-300.fc30.x86_64, modules.dep.tmp, /lib/modules/5.0.14-300.fc30.x86_64, modules.dep): No such file or directory

However, if I call dkms autoinstall manually after boot, module installs just fine.

This message is a reminder that Fedora 29 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '29'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 29 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Unchanged

DKMS 2.8.2 has been pushed to Bodhi right now, if someone wants to make a test.

I was seeing the same issue.

Using dkms-2.8.2-1 from updates-testing and configuring the sign_tool in /etc/dkms/framework.conf makes "dkms autoinstall" work again.

(In reply to Simon Lanzmich from comment #11)
> I was seeing the same issue.
> 
> Using dkms-2.8.2-1 from updates-testing and configuring the sign_tool in
> /etc/dkms/framework.conf makes "dkms autoinstall" work again.

Does it also work without the sign_tool being set?
Btw, just created an update for 2.8.3.

Running a POST_BUILD script with dkms-2.8.3-1.fc32 still shows the original issue, environment variables "$kernelver" and "$arch" are only set with "dkms install", not "dkms autoinstall".

This message is a reminder that Fedora 31 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '31'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 31 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Fedora 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.