Ubuntu
snapd package

Timer services are listed in "snap info" as disabled

Bug #1784384 reported by Robie Basak
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
snapd (Ubuntu)
Confirmed
Low
Ian Johnson

Bug Description

$ snap install --edge --classic certbot
...
$ snap info certbot
...
services:
  certbot.renew: oneshot, disabled, inactive
...
$

This is misleading. Actually "systemctl status snap.certbot.renew.timer" shows that the timer is "active (waiting)". It is only the underlying service that is disabled and inactive - because it only fires when the timer makes it fire. So everything is working fine, but I think users could be misled into thinking that there is a problem with certbot renewals.

Suggestion for improvement: when a service has an underlying timer, could we display something more positive in the output of "snap info" instead? Eg. "certbot.renew: oneshot, awaiting-timer".

On snapd 2.34.2 on Xenial.

Revision history for this message
Ian Johnson (anonymouse67) wrote :

This is a known issue, and we hope to fix this as part of some upcoming work surrounding services in snapd. See https://forum.snapcraft.io/t/how-to-manage-services-with-sockets-timers/7904/8?u=ijohnson for a current status around these efforts.

Assigning to myself for now

Changed in snapd (Ubuntu):
assignee: nobody → Ian Johnson (anonymouse67)
importance: Undecided → Low
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.