This looks like a duplicate of bug 2169328 (snapd), filed against the wrong package. The trigger is snapd 2.77.1, not the apparmor deb.
snapd compiles snap profiles with its own vendored apparmor_parser, not the system one. On our 8-node Ubuntu 24.04 cluster (kernel 6.17): - system apparmor deb: 4.0.1really4.0.1-0ubuntu0.24.04.5, unchanged since 2026-03-21 - snapd 2.76.3 vendored parser: 4.1.7, no denials - snapd 2.77.1 vendored parser: 5.0.2, same file_perm class="net" send/receive denials as reported here, on snap.microceph.*, snap.microovn.* and snap.microcloud.daemon The denials started the minute snapd auto-refreshed to 2.77.1, with no apparmor deb change. "snap revert snapd" to 2.76.3 + "snap refresh --hold snapd" fixed it immediately on every node. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2169387 Title: AppArmor 4.0.1 snap profiles deny TCP network traffic (file_perm class="net") for snappy apps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2169387/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
