snapd

`snap services` should indicate when services are a oneshot

Bug #1795947 reported by Dan Watkins
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
snapd
Triaged
Low
Unassigned

Bug Description

When I run `snap services` with a couple of Canonical snaps installed, I see the following:

Service Startup Current
canonical-livepatch.canonical-livepatchd enabled inactive
lxd.activate enabled inactive
lxd.daemon enabled active

This suggests to me that canonical-livepatch.canonical-livepatchd and lxd.activate are in some way broken (as if they're enabled it's reasonable to think that they should be active). In canonical-livepatch's case, my intuition is correct; I'm on 18.10 so the service fails to start. lxd.activate, on the other hand, is a oneshot service, so it's not in an error state at all; it's done everything it needs to do.

It would be good if `snap services` distinguished between these two cases.

Revision history for this message
Zygmunt Krynicki (zyga) wrote :

This feels like a papercut but it also needs UX design. I'll relay this issue to my colleague who is looking into snap service management now.

affects: snappy → snapd
Changed in snapd:
status: New → Triaged
importance: Undecided → Low
Revision history for this message
Ian Johnson (anonymouse67) wrote :

We will be working on some UX changes to `snap services`, namely the changes mentioned at https://forum.snapcraft.io/t/how-to-manage-services-with-sockets-timers/7904/8?u=ijohnson

We don't currently have plans to expose the type of service in the snap services output, but we are exploring having a `snap services --verbose` which seems like a natural place to put this.

Changed in snapd:
assignee: nobody → Ian Johnson (anonymouse67)
Ian Johnson (anonymouse67)
Changed in snapd:
assignee: Ian Johnson (anonymouse67) → nobody
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.