Comment 5 for bug 1735424

Trying to find dormant bugs that could/should be resolved ...

To summarize (for mysql8.0) as of today:

Build:
-- Looking for include file numa.h
-- Looking for include file numa.h - found
-- Looking for include file numaif.h
-- Looking for include file numaif.h - found
-- Performing Test HAVE_LIBNUMA
-- Performing Test HAVE_LIBNUMA - Success

it is enabled, libnuma shows in dependencies, ...
All fine feature wise.

The apparmor rule was fixed in 5.7.17

commit ba7bd14c0eff8c68664c66a0e0d241fafc142a5d
Author: Bjoern Boschman <email address hidden>
Date: Wed Dec 14 13:36:55 2016 +0100

    Imported Upstream version 5.7.17

diff --git a/packaging/deb-in/extra/apparmor-profile b/packaging/deb-in/extra/apparmor-profile
index 83ed6ec1e..8004069fc 100644
--- a/packaging/deb-in/extra/apparmor-profile
+++ b/packaging/deb-in/extra/apparmor-profile
@@ -9,6 +9,9 @@

 # Allow system resource access
   /sys/devices/system/cpu/ r,
+ /sys/devices/system/node/ r,
+ /sys/devices/system/node/** r,
+ /proc/*/status r,
   capability sys_resource,
   capability dac_override,
   capability setuid,

But the report and tests were with later versions e.g. reported with 5.7.20.

Clearly on a Kinetic system I see the right rules being present.

@Lena / Robie / Larse - maybe that is an easy test to recheck if at least in recent mysql-8.0 this can be enabled and works without any apparmor issues.
And if there are, that sounds like an easy but helpful fix for this cycles merge time.