I noticed this in the output of a unattended update of some satellite machines
Configuration file ‘/etc/apparmor.d/old_apparmor’
==> Deleted (by you or by a script) since installation.
==> Package distributor has shipped an updated version.
==> Keeping old config file as default.
Configuration file ‘/etc/apparmor.d/usr.sbin.mysqld.in2’
==> Deleted (by you or by a script) since installation.
==> Package distributor has shipped an updated version.
==> Keeping old config file as default
Should these be using the new distributed versions? These files were never modified by anything other than percona packages or scripts.
Hi @Matthew_Lenz_L1T ,
No, /etc/apparmor.d/usr.sbin.mysqld is the only apparmor config file that we need.
/etc/apparmor.d/old_apparmor and /etc/apparmor.d/usr.sbin.mysqld.in2 are installed and removed during the post-installation phase, which is the reason you’re getting the mentioned output. This was done when telemetry was introduced, to add telemetry rules to the apparmor config file on systems where it isn’t updated with the new version. Thank you.
So given that output which files should be removed or replaced?
We don’t have to explicitly remove or replace any files.
/etc/apparmor.d/old_apparmor and /etc/apparmor.d/usr.sbin.mysqld.in2 are removed by the post-installation script of the package. The update you noticed during the installation is because of some new rules being added to the apparmor config files in this release.