Bug 1447458

Summary:	Timer unit can't be properly activated
Product:	[Fedora] Fedora EPEL	Reporter:	Anatole Denis <rhbz>
Component:	certbot	Assignee:	James Hogarth <james.hogarth>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	epel7	CC:	itamar, james.hogarth, nb, nick, rbu
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-05-02 21:19:15 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Anatole Denis 2017-05-02 21:08:59 UTC

Description of problem:

There is a typo in certbot-renew.timer, the line

WantedBy=timer.target

refers to a nonexisting target. It should be

WantedBy=timers.target

As a consequence enabling the timer unit doesn't ensure it is started appropriately on boot

Version-Release number of selected component (if applicable): 0.13.0-2.el7

How reproducible: always


Steps to Reproduce:
1. Enable the certbot-renew.timer unit
2. Restart timers.target or the machine

Actual results:

The timer unit is not started (systemctl status certbot-renew.timer or systemctl list-timers)

Expected results:

The timer unit is started and appears in systemctl list-timers

Comment 1 Anatole Denis 2017-05-02 21:19:15 UTC

Sorry I completely forgot to check whether it was fixed in updates-testing (and it is)

All my apologies for the spam

*** This bug has been marked as a duplicate of bug 1439957 ***