Broken AppArmor profile after upgrade

Description

This issue is related to .

We have exactly the same implementation of AppArmor profiles installation in percona-xtradb-cluster-server.postinst file, so we will see the same issue as reported for PS.

After fixing the issue in PS, we need to port the same solution for PXC

Environment

None

Smart Checklist

Activity

Show:

puneet.kaushik September 16, 2024 at 10:14 AM

Fixed ! verified with new installation and upgrade.

Lenz Grimmer November 19, 2021 at 7:56 AM

No objections - thanks for the investigation!

Kamil Holubicki November 18, 2021 at 11:42 PM

OK, my 2nd thought is that this is not a blocker.

  1. AA was introduced in 8.0.23 ()

  2. From that time AA profile files were not changed (no need to update)

  3. As per the bug description, AA profile is installed properly only for fresh installation (not update)

  4. If someone updated from 8.0.22 to 8.0.23, AA would not be configured properly (as AA profile files are not installed properly in case of an update). But I cannot recall any complaints about this issue.

If there are no objections, let's fix it in the next PXC release (after 8.0.25)

Kamil Holubicki November 18, 2021 at 3:39 PM

,

I was wrong with the workaround. It will not do the job. We need a fix or manual installation of AA profiles after the upgrade.

Lenz Grimmer November 18, 2021 at 3:06 PM

Adding for visibility.
As the fix for has not been merged yet and a workaround exists, I'd suggest to proceed with the 8.0.25 release, but adding this as a "known issue" to the release notes, including instructions on how to fix the profiles manually. - what's your take?

Done

Details

Assignee

Reporter

Needs QA

Yes

Time tracking

20m logged20m remaining

Components

Affects versions

Priority

Smart Checklist

Created November 18, 2021 at 2:53 PM
Updated September 18, 2024 at 4:01 PM
Resolved September 16, 2024 at 10:14 AM