|Summary:||certbot.timer doesn't run after reboot despite being enabled|
|Product:||[Fedora] Fedora||Reporter:||Dominik 'Rathann' Mierzejewski <dominik>|
|Component:||certbot||Assignee:||James Hogarth <james.hogarth>|
|Status:||CLOSED EOL||QA Contact:||Fedora Extras Quality Assurance <extras-qa>|
|Version:||26||CC:||elyscape, itamar, james.hogarth, nb, nick, rbu|
|Fixed In Version:||Doc Type:||If docs needed, set a value|
|Doc Text:||Story Points:||---|
|Last Closed:||2018-05-29 11:21:44 UTC||Type:||Bug|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Cloudforms Team:||---||Target Upstream Version:|
Description Dominik 'Rathann' Mierzejewski 2018-04-06 06:46:10 UTC
Description of problem: After each reboot, I have to manually run systemctl start certbot.timer. Otherwise it doesn't run despite being enabled. Version-Release number of selected component (if applicable): certbot-0.22.2-1.fc26.noarch How reproducible: Always Steps to Reproduce: 1. reboot 2. systemctl status certbot-renew.timer Actual results: ● certbot-renew.timer - This is the timer to set the schedule for automated renewals Loaded: loaded (/usr/lib/systemd/system/certbot-renew.timer; enabled; vendor preset: disabled) Active: inactive (dead) Expected results: ● certbot-renew.timer - This is the timer to set the schedule for automated renewals Loaded: loaded (/usr/lib/systemd/system/certbot-renew.timer; enabled; vendor preset: disabled) Active: active (waiting) since Fri 2018-04-06 08:41:05 CEST; 32s ago
Comment 1 Eli Young 2018-05-02 16:49:43 UTC
Have you tried running systemctl disable certbot.timer and then systemctl enable certbot.timer? I wonder if maybe the want symlink wasn't correctly installed.
Comment 2 Fedora End Of Life 2018-05-03 07:53:07 UTC
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 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 '26'. 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 26 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.
Comment 3 Fedora End Of Life 2018-05-29 11:21:44 UTC
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 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.