Additional findings:

We were able to reproduce the issue with both Apache Pulsar components
and PostgreSQL workloads running on Kubernetes/K3s.

The issue disappears when either:

sysctl -w kernel.apparmor_restrict_unprivileged_unconfined=0

is applied, or when the affected workloads are configured with:

appArmorProfile:
  type: Unconfined

After recreating the affected pods, both Pulsar and PostgreSQL start
successfully on kernel 7.0.0-42.

This strongly suggests that Bug #2172832 is another manifestation of the
same AppArmor/profile-stacking signal handling regression discussed in
Bug #2172422 and Bug #2172640, rather than an application-specific issue
in Pulsar or PostgreSQL.

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

Title:
  Compatibility Issue with Ubuntu 26.04 Kernel 7.0.0-42

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


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

Reply via email to