snapd doesn't clean up imported (snap) assertions

Bug #1673539 reported by Didier Roche on 2017-03-16
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
snapd
Medium
Unassigned
snapd (Ubuntu)
Medium
Unassigned

Bug Description

1. Install a snap from the store or import an assertion manually with snap ack.
2. Remove than snap from the system.

The assertion is kept on the system. It seems that we are collecting more and more assertions over time which can be sizeable after some usage and updates in /var/lib/snapd/assertions/. I think that once the snap is removed explicitely of the system or if a revision isn't used/available after a while, the assertions should be garbaged collected.

$ snap version
snap 2.23.1
snapd 2.23.1
series 16
ubuntu 16.04
kernel 4.4.0-66-generic

Didier Roche (didrocks) on 2017-03-16
description: updated
description: updated
John Lenton (chipaca) wrote :

Could you share the output of “sudo du -sh /var/lib/snapd/assertions/” on a system where you consider this to be sizeable?

Michael Vogt (mvo) on 2018-01-17
affects: snappy → snapd
Changed in snapd (Ubuntu):
status: New → Triaged
Changed in snapd:
status: New → Triaged
importance: Undecided → Medium
Changed in snapd (Ubuntu):
importance: Undecided → Medium
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers