Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

If you use "--profile" it will create a playbook based on the profile, not the results scan. This is a corrected example:

oscap xccdf generate fix --fix-type ansible --result-id
"" --output hipaa-remediations.yml hipaa-results.xml

Took me like, 2 hours to find this answer. Here's the blog post that helped me. http://redhatgov.io/workshops/rhel_8/exercise1.7/

Try it yourself. The profile ansible playbook will have:
# This Ansible Playbook is generated from an OpenSCAP profile without preliminary evaluation.
# It attempts to fix every selected rule, even if the system is already compliant.
at the top.

Reported by: xhk416x

https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/security_hardening/scanning-the-system-for-configuration-compliance-and-vulnerabilities_security-hardening#annotations:fb7b6d6a-51e9-4aad-8c23-036fcd798ce4

Annotation: Chapter 8. Scanning the system for configuration compliance and vulnerabilities of the "Security Hardening" title

Thanks a lot for reporting this! I discussed this with the Compliance SMEs and updated both RHEL 8 and RHEL 9 documentation. The changes should be visible here in a few hours:

https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/security_hardening/scanning-the-system-for-configuration-compliance-and-vulnerabilities_security-hardening#creating-a-remediation-ansible-playbook-to-align-the-system-with-a-specific-baseline_scanning-the-system-for-configuration-compliance-and-vulnerabilities

https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html/security_hardening/scanning-the-system-for-configuration-compliance-and-vulnerabilities_security-hardening#creating-a-remediation-ansible-playbook-to-align-the-system-with-a-specific-baseline_scanning-the-system-for-configuration-compliance-and-vulnerabilities