If you seed a snap, then you also need to seed that snap's base, and
snaps providing any plugs that snap requires, otherwise it'll fail to
seed.
A failure to seed it pretty bad, as snapd will be stuck in a loop trying
to do that. I don't think this is a bug in snapd, because if you have
network, this same retrying will mean that the missing bases and missing
content interfaces that have default providers specified will be
downloaded automatically, and seeding will succeed. There might be some
things we can do to make it use less CPU, but they're a lot of work. The
only *sensible* thing snapd could in this case is alert the user,
although there's nothing the user can do beyond contact the creator of
the seed so it's not very useful.
Marking as "Won't fix" for snapd. Feel free to point out why I'm wrong
on that.
** Changed in: snapd (Ubuntu)
Status: Confirmed => Won't Fix
** Summary changed:
- Live 18.04 with persistence snapd high CPU usage
+ Live 18.04 with broken seed causes snapd high CPU usage
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767896
Title:
Live 18.04 with broken seed causes snapd high CPU usage
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1767896/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
