Make hardening crypto policies by Ansible idempotent#14001
Merged
Conversation
|
@jan-cerny: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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. I understand the commands that are listed here. |
Collaborator
Author
|
/packit build |
Mab879
approved these changes
Oct 13, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description:
This PR makes Ansible remediation in these rules idempotent:
Rationale:
Resolves: https://issues.redhat.com/browse/OPENSCAP-6230
Review Hints:
./build_product --playbook-per-rule rhel8hosts: allinbuild/rhel8/playbooks/all/harden_openssl_crypto_policy.ymlansible-playbook -u root -i YOUR_IP, build/rhel8/playbooks/all/harden_openssl_crypto_policy.ymlat least twice and compare the output of the first run with the second run and so on, verify that the second and next runs don't change anything and that the output contains only "ok" or "skipping"build/rhel8/playbooks/stig/harden_sshd_ciphers_opensshserver_conf_crypto_policy.ymlandbuild/rhel8/playbooks/stig/harden_sshd_macs_opensshserver_conf_crypto_policy.yml--remediate-using ansible. Ensure your automatus back end virtual machine contains at least openscap 1.3.12. This version is necessary because of the negative number in OVAL.