Bug 1983391 - fetch-crl systemd timer unit broken
Summary: fetch-crl systemd timer unit broken
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: fetch-crl
Version: 34
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Steve Traylen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-07-18 04:08 UTC by Mattias Ellert
Modified: 2024-11-22 02:55 UTC (History)
1 user (show)

Fixed In Version: fetch-crl-3.0.21-2.fc34 fetch-crl-3.0.22-2.el8
Clone Of:
Environment:
Last Closed: 2021-08-25 19:53:18 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Mattias Ellert 2021-07-18 04:08:22 UTC
Description of problem:

With the current systemd version on Fedora 34 the fetch-crl timer unit is broken.

# systemctl status fetch-crl.timer 
● fetch-crl.timer - Run fetch-crl every 6 hours
     Loaded: loaded (/usr/lib/systemd/system/fetch-crl.timer; enabled; vendor p>
     Active: active (elapsed) since Sun 2021-07-18 05:22:31 CEST; 4min 28s ago
    Trigger: n/a
   Triggers: ● fetch-crl.service

I.e. the timer is never triggered.

If I remove the line "Persistent=true" from the timer unit file it starts working again:

# systemctl status fetch-crl.timer 
● fetch-crl.timer - Run fetch-crl every 6 hours
     Loaded: loaded (/usr/lib/systemd/system/fetch-crl.timer; enabled; vendor p>
     Active: active (waiting) since Sun 2021-07-18 05:30:38 CEST; 8min ago
    Trigger: Sun 2021-07-18 11:31:16 CEST; 5h 51min left
   Triggers: ● fetch-crl.service

"man systemd.timer" says about the Persistent option:
Note that this setting only has an effect on timers configured with OnCalendar=.

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

fetch-crl-3.0.21-1.fc34

How reproducible:

Always

Steps to Reproduce:
1. Enable fetch-crl systemd timer

Actual results:

fetch-crl service not triggered by timer.

Expected results:

fetch-crl service triggered by timer.

Additional info:

Comment 1 Fedora Update System 2021-08-16 07:48:59 UTC
FEDORA-2021-9e8d159505 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-9e8d159505

Comment 2 Fedora Update System 2021-08-17 01:08:59 UTC
FEDORA-2021-9e8d159505 has been pushed to the Fedora 34 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-9e8d159505`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-9e8d159505

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

Comment 3 Fedora Update System 2021-08-25 19:53:18 UTC
FEDORA-2021-9e8d159505 has been pushed to the Fedora 34 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 4 Fedora Update System 2024-11-13 15:26:44 UTC
FEDORA-EPEL-2024-476551b038 (fetch-crl-3.0.22-2.el8) has been submitted as an update to Fedora EPEL 8.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-476551b038

Comment 5 Fedora Update System 2024-11-14 03:15:03 UTC
FEDORA-EPEL-2024-476551b038 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-2024-476551b038

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

Comment 6 Fedora Update System 2024-11-22 02:55:12 UTC
FEDORA-EPEL-2024-476551b038 (fetch-crl-3.0.22-2.el8) has been pushed to the Fedora EPEL 8 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.