Hello Zyga, Mohit,
thanks for waiting, I have the first solution:
diff --git a/scripts/test-apparmor.py b/scripts/test-apparmor.py
index 5a79e837..bce4c6b8 100755
--- a/scripts/test-apparmor.py
+++ b/scripts/test-apparmor.py
@@ -342,6 +342,7 @@ exit 0'''
# try and find a snapd snap with a vendored apparmor_parser
has_vendored_apparmor = False
for track in ["latest/stable", "latest/candidate", "latest/beta",
"latest/edge"]:
+ testlib.cmd(['systemctl', 'reset-failed', 'snapd.service',
'snapd.socket'])
self.refresh_snap("snapd", track=track)
rc, report = testlib.cmd(['snap', 'debug', 'sandbox-features',
'--required', 'apparmor:parser:snapd-internal'])
if rc == 0:
tested on 10 affected Google instances and it appears to fix the problem.
Maybe you want to commit this into
https://code.launchpad.net/qa-regression-testing (repo not in our hand, it's
from the security team)?
Thanks!
--
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
