Bug 2101946 - The dkms service doesn't start anymore in version 3.0.4
Summary: The dkms service doesn't start anymore in version 3.0.4
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: dkms
Version: epel7
Hardware: All
OS: All
unspecified
urgent
Target Milestone: ---
Assignee: Simone Caronni
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-06-28 21:10 UTC by Kilian Cavalotti
Modified: 2022-07-08 02:23 UTC (History)
2 users (show)

Fixed In Version: dkms-3.0.5-1.fc36 dkms-3.0.5-1.fc35 dkms-3.0.5-1.el9 dkms-3.0.5-1.el8 dkms-3.0.5-1.el7
Clone Of:
Environment:
Last Closed: 2022-07-08 01:16:05 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Kilian Cavalotti 2022-06-28 21:10:22 UTC
Description of problem:

The dkms service doesn't start anymore in version 3.0.4


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

dkms-3.0.4-1.el7.noarch


How reproducible:

100% of the time


Steps to Reproduce:
1. update dkms RPM
2. start the dkms service with `systemctl start dkms`
3. note the failure


Actual results:

The service fails to start with the following error:

systemd[1]: [/usr/lib/systemd/system/dkms.service:9] Executable path is not absolute, ignoring: dkms autoinstall --verbose --kernelver %v
systemd[1]: dkms.service lacks both ExecStart= and ExecStop= setting. Refusing.
systemd[1]: Cannot add dependency job for unit dkms.service, ignoring: Unit is not loaded properly: Invalid argument.


Expected results:

The dkms service starts without any error, like in version 3.0.3


Additional info:

In /usr/lib/systemd/system/dkms.service, the ExecStart line has been modified from:

ExecStart=/bin/sh -c 'dkms autoinstall --verbose --kernelver $(uname -r)'

in version 3.0.3, to:

ExecStart=dkms autoinstall --verbose --kernelver %v

in version 3.0.4, which makes systemd ignore the whole ExecStart line, as the executable path is not absolute.

Comment 1 Fedora Update System 2022-06-29 11:05:25 UTC
FEDORA-2022-ed5422c99c has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-ed5422c99c

Comment 2 Fedora Update System 2022-06-29 11:05:26 UTC
FEDORA-EPEL-2022-c7428ccae1 has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-c7428ccae1

Comment 3 Fedora Update System 2022-06-29 11:05:27 UTC
FEDORA-EPEL-2022-f382c4b864 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-f382c4b864

Comment 4 Fedora Update System 2022-06-29 11:05:29 UTC
FEDORA-EPEL-2022-992a650cf2 has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-992a650cf2

Comment 5 Fedora Update System 2022-06-29 11:05:30 UTC
FEDORA-2022-38eede1761 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-38eede1761

Comment 6 Fedora Update System 2022-06-30 01:24:59 UTC
FEDORA-2022-38eede1761 has been pushed to the Fedora 35 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-38eede1761`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-38eede1761

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 7 Fedora Update System 2022-06-30 01:33:21 UTC
FEDORA-2022-ed5422c99c has been pushed to the Fedora 36 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-ed5422c99c`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-ed5422c99c

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 8 Fedora Update System 2022-06-30 02:10:04 UTC
FEDORA-EPEL-2022-992a650cf2 has been pushed to the Fedora EPEL 9 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-992a650cf2

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 9 Fedora Update System 2022-06-30 02:19:52 UTC
FEDORA-EPEL-2022-c7428ccae1 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-2022-c7428ccae1

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 10 Fedora Update System 2022-06-30 02:34:20 UTC
FEDORA-EPEL-2022-f382c4b864 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-2022-f382c4b864

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 11 Fedora Update System 2022-07-08 01:16:05 UTC
FEDORA-2022-ed5422c99c has been pushed to the Fedora 36 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 12 Fedora Update System 2022-07-08 01:36:46 UTC
FEDORA-2022-38eede1761 has been pushed to the Fedora 35 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 13 Fedora Update System 2022-07-08 01:44:21 UTC
FEDORA-EPEL-2022-992a650cf2 has been pushed to the Fedora EPEL 9 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 14 Fedora Update System 2022-07-08 02:08:44 UTC
FEDORA-EPEL-2022-c7428ccae1 has been pushed to the Fedora EPEL 8 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 15 Fedora Update System 2022-07-08 02:23:41 UTC
FEDORA-EPEL-2022-f382c4b864 has been pushed to the Fedora EPEL 7 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.