The system key is only rewritten if this is required. Normally it is not modified.
The question now is: what has changed that made the system key differ? One thing we did observe was /snap/core/$current changing without a complete snapd re-start. Perhaps something was pinging snapd over the API and it failed to complete a restart after a core refresh? Can you check with "snap changes" if there was a corresponding refresh of "core" or "snapd" sometime earlier than the system-key rewrite and in close proximity to the moment LXD started hanging? System key contains interesting details of the system including build IDs of "snapd", some kernel and userspace library features. One other possibility is update of seccomp or apparmor that might have happened. Is "/usr/lib/snapd/snap-seccomp" and "/snap/core/current/usr/lib/snapd /snap-seccomp" linked statically on s390x? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873004 Title: lxd interaction blocked until snapd was restarted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1873004/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
