Additional observations and potentially related reports.

Further investigation suggests that this is not a DNS resolution issue.

DNS resolution itself continues to work correctly on the affected
systems:

    getent hosts pulsar-bookie

returns the expected result under both 7.0.0-38-generic and
7.0.0-42-generic.

The failure appears to occur during nslookup shutdown rather than
during name resolution itself. The following command consistently
reproduces the issue on affected systems:

    nslookup -timeout=10 pulsar-bookie | grep Name | wc -l

Output:

    ../../../lib/isc/app.c:399: fatal error:
    isc_app_shutdown() kill: Permission denied
    Segmentation fault (core dumped)

At the same time, the kernel audit log reports an AppArmor signal
denial:

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

This suggests that nslookup successfully completes DNS resolution
but subsequently fails while shutting down because signal handling
inside the container is denied by AppArmor.

This issue may be related to the following reports:

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

That report also describes AppArmor signal denials involving stacked
profiles ("//&...") introduced with kernel 7.0.0-42. Although the
affected application differs, the underlying symptom appears similar:
signal operations inside containerized workloads are denied, causing
application malfunction.

Bug #2172422:
"Regression 7.0.0-42/-43: Go 1.24 programs livelock..."

This may indicate a broader regression affecting process
communication, synchronization, or signal handling in containerized
applications on kernels 7.0.0-42 and newer.

The common characteristics are:

- Works correctly on kernel 7.0.0-38-generic
- Regresses on kernel 7.0.0-42-generic
- Only containerized workloads are affected
- AppArmor signal denials are observed
- Stacked AppArmor profiles ("//&...") appear in audit logs

For this reason, the issue may share the same root cause as the
regression described in Bug #2172640, namely recent changes in
AppArmor profile stacking and signal handling for containerized
processes.

** Tags added: apparmor regression-update resolute

-- 
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