snap stop <snap>.<svc> does not create a change associated with <snap>

Bug #1880560 reported by Ian Johnson on 2020-05-25
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
snapd
Medium
Maciej Borzecki

Bug Description

If I run `snap restart lxd`, the change that is generated is visible from `snap changes lxd`, however if I run `snap stop lxd.daemon` the change that is generated is not visible from `snap changes lxd`. Observe:

$ snap stop lxd.daemon
Stopped.
$ snap changes
ID Status Spawn Ready Summary
18815 Done today at 07:39 CDT today at 07:39 CDT Running service command
$ snap changes lxd
error: no changes found
$ snap restart lxd
Restarted.
$ snap changes
ID Status Spawn Ready Summary
18815 Done today at 07:39 CDT today at 07:39 CDT Running service command
18816 Done today at 07:40 CDT today at 07:40 CDT Running service command
$ snap changes lxd
ID Status Spawn Ready Summary
18816 Done today at 07:40 CDT today at 07:40 CDT Running service command

description: updated
summary: - snap stop <snap> does not create a change associated with <snap>
+ snap stop <snap>.<svc> does not create a change associated with <snap>
Changed in snapd:
status: New → Confirmed
assignee: nobody → Maciej Borzecki (maciek-borzecki)
Changed in snapd:
status: Confirmed → In Progress

Opened a PR to address this: https://github.com/snapcore/snapd/pull/8766

Changed in snapd:
importance: Undecided → Medium
Changed in snapd:
status: In Progress → Fix Committed
Zygmunt Krynicki (zyga) on 2020-06-23
Changed in snapd:
milestone: none → 2.46
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers