I would like to provide an additional data point from a Kubernetes
workload that is unrelated to PostgreSQL.

We reproduced the same stacked AppArmor label behaviour on Ubuntu 26.04
with kernel 7.0.0-42 while deploying Cumulocity Edge 2026.0.4 on K3s.

In this environment, several application components remained permanently
in Init state although DNS resolution itself continued to work
correctly.

The affected startup checks relied on:

  nslookup <service> | grep Name | wc -l

DNS lookups returned valid records, but nslookup terminated abnormally
and the init scripts never completed.

Kernel audit logs showed:

  apparmor="DENIED"
  operation="signal"
  class="signal"
  profile="nslookup"
  requested_mask="receive"
  denied_mask="receive"
  signal=abrt
  peer="cri-containerd.apparmor.d//&nslookup"

The issue disappeared after allowing communication with the stacked
profile label:

  signal (send,receive) peer=cri-containerd.apparmor.d//&nslookup,

as well as the more general stacked-label rule:

  signal (send,receive) peer=cri-containerd.apparmor.d//&*,

This suggests that the regression is not limited to PostgreSQL signal
handling.

In our environment the same behavioural change affected:
- PostgreSQL-based workloads
- readiness checks using nslookup
- Kubernetes init containers
- application startup sequencing

The common denominator was AppArmor signal denials involving stacked
labels such as:

  cri-containerd.apparmor.d//&unconfined
  cri-containerd.apparmor.d//&nslookup

This may help define the scope of the regression more broadly than a
PostgreSQL-specific issue.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2172640

Title:
  Regression in 7.0.0-42: AppArmor forced "//&unconfined" stack on
  container processes blocks signals between them (PostgreSQL hangs)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2172640/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to