Fix the ctest of python-unit-utils/oscal

[alanmcanonical]

Description:

• Fix the ctest of python-unit-utils/oscal by bumping the compliance-trestle version in requirement
• Bump the version of compliance-trestle from 2.4.0 to 3.6.0

Rationale:

• Solved the issue ctest python-unit-utils/oscal fails on Ubuntu 24.04 #12795 and several workflow failures of Minor typo fix #12785 Ubuntu 24.04: Implement rule 5.3.3.3.1 Ensure password history remember is configured #12784 Ubuntu 24.04: Implement rule 5.3.3.4.2 Ensure pam_unix does not include remember #12780 Ubuntu 24.04: Implement rule 5.3.2.2 Ensure pam_faillock module is enabled #12779 Ubuntu 24.04: Implement rule 5.4.2.2 Ensure root is the only GID 0 account #12777 Ubuntu 24.04: Implement rule 5.3.3.1.2 Ensure password unlock time is configured #12772 Ubuntu 24.04: Implement 5.3.3.4.1 Ensure pam_unix does not include nullok #12770

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

[github-actions]

Start a new ephemeral environment with changes proposed in this pull request:

Fedora Environment

Oracle Linux 8 Environment

[Mab879]

@jpower432 Is there any issues with us upgrading to the latest version of Trestle?

[codeclimate]

Code Climate has analyzed commit 9452e26 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.6% (0.0% change).

View more on Code Climate.

[jpower432]

@jpower432 Is there any issues with us upgrading to the latest version of Trestle?

@Mab879 I don't see any issues with upgrading. The update to v3 includes changes to the OSCAL Python classes in trestle, but no breaking changes with OSCAL itself (OSCAL 1.0.4 -> OSCAL 1.1.2).

[Mab879]

/packit retest-failed

[Mab879]

/packit retest-failed

[Mab879]

/packit retest-failed

[marcusburghardt]

LGTM. I also reviewed a similar PR #12762

[marcusburghardt]

Thanks for working on this @alanmcanonical @Mab879 and @jpower432 . I just reviewed a similar PR #12762 but that one is not enough to make CI tests green. So, I will prioritize this and monitor the CI tests along this morning.