We managed to reproduce this again in GKE environment. I logged in after the failure and re-refreshed snapd snap to beta (2.77, revision 27911) successfully.
Logs from snapd.failure.service: Aug 28 07:26:25 n-lgke-gke-6-8-c4hcpu4-u-qrt-apparmor.c.ubuntu-devel.internal systemd[1]: Starting snapd.failure.service - Failure handling of the snapd snap... Aug 28 07:26:25 n-lgke-gke-6-8-c4hcpu4-u-qrt-apparmor.c.ubuntu-devel.internal snap-failure[12914]: cmd_snapd.go:163: found previous revision of snapd snap: 27738 Aug 28 07:26:25 n-lgke-gke-6-8-c4hcpu4-u-qrt-apparmor.c.ubuntu-devel.internal snap-failure[12914]: cmd_snapd.go:169: stopping snapd socket Aug 28 07:26:25 n-lgke-gke-6-8-c4hcpu4-u-qrt-apparmor.c.ubuntu-devel.internal snap-failure[12914]: cmd_snapd.go:176: restoring invoking snapd from: /snap/snapd/27738/usr/lib/snapd/snapd Aug 28 07:26:25 n-lgke-gke-6-8-c4hcpu4-u-qrt-apparmor.c.ubuntu-devel.internal snap-failure[12921]: Running as unit: run-u107.service; invocation ID: 50e8a1f233a143b3b325044e0ea0b85a Aug 28 07:26:30 n-lgke-gke-6-8-c4hcpu4-u-qrt-apparmor.c.ubuntu-devel.internal snap-failure[12921]: Finished with result: success Aug 28 07:26:30 n-lgke-gke-6-8-c4hcpu4-u-qrt-apparmor.c.ubuntu-devel.internal snap-failure[12921]: Main processes terminated with: code=exited/status=0 Aug 28 07:26:30 n-lgke-gke-6-8-c4hcpu4-u-qrt-apparmor.c.ubuntu-devel.internal snap-failure[12921]: Service runtime: 4.372s Aug 28 07:26:30 n-lgke-gke-6-8-c4hcpu4-u-qrt-apparmor.c.ubuntu-devel.internal snap-failure[12921]: CPU time consumed: 1.631s Aug 28 07:26:30 n-lgke-gke-6-8-c4hcpu4-u-qrt-apparmor.c.ubuntu-devel.internal snap-failure[12921]: Memory peak: 256.0K Aug 28 07:26:30 n-lgke-gke-6-8-c4hcpu4-u-qrt-apparmor.c.ubuntu-devel.internal snap-failure[12921]: Memory swap peak: 0B Aug 28 07:26:30 n-lgke-gke-6-8-c4hcpu4-u-qrt-apparmor.c.ubuntu-devel.internal snap-failure[13104]: active Aug 28 07:26:30 n-lgke-gke-6-8-c4hcpu4-u-qrt-apparmor.c.ubuntu-devel.internal snap-failure[13104]: activating Aug 28 07:26:30 n-lgke-gke-6-8-c4hcpu4-u-qrt-apparmor.c.ubuntu-devel.internal snap-failure[13106]: active Aug 28 07:26:30 n-lgke-gke-6-8-c4hcpu4-u-qrt-apparmor.c.ubuntu-devel.internal snap-failure[13106]: activating Aug 28 07:26:30 n-lgke-gke-6-8-c4hcpu4-u-qrt-apparmor.c.ubuntu-devel.internal snap-failure[12914]: cmd_snapd.go:212: snapd is active again, sockets are available, nothing more to do Aug 28 07:26:30 n-lgke-gke-6-8-c4hcpu4-u-qrt-apparmor.c.ubuntu-devel.internal systemd[1]: snapd.failure.service: Deactivated successfully. Aug 28 07:26:30 n-lgke-gke-6-8-c4hcpu4-u-qrt-apparmor.c.ubuntu-devel.internal systemd[1]: Finished snapd.failure.service - Failure handling of the snapd snap. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2165135 Title: test_snapd_snap_with_vendored_apparmor from ubuntu_qrt_apparmor failed to refresh snapd to latest/beta (2.76.3+ubuntu24.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2165135/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
