[Ubuntu2404] Only enforce valid profile to avoid apparmor issue

[alanmcanonical]

Description:

• Only enforce valid profile file instead of recursive enforce

Rationale:

• Current version of noble apparmor-utils has issue, although it's been fixed, this patch hasn't landed in noble yet. We need to find all the profiles then we can enforce to mitigate this issue

[openshift-ci]

Hi @alanmcanonical. Thanks for your PR.

I'm waiting for a ComplianceAsCode member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[codeclimate]

Code Climate has analyzed commit 02ca445 and detected 0 issues on this pull request.

The test coverage on the diff in this pull request is 100.0% (50% is the threshold).

This pull request will bring the total coverage in the repository to 61.9% (0.0% change).

View more on Code Climate.

[alanmcanonical]

Here is the tests result on Ubuntu noble vm :

[dodys]

@alanmcanonical the tests are failing, could you please take a look?

[alanmcanonical]

@alanmcanonical the tests are failing, could you please take a look?

It's due to apparmor applicability in container, the vm tests results as pasted work fine

[mpurg]

lgtm!

[dodys]

lgtm, thanks!