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.

What problem/issue/behavior are you having trouble with?  What do you expect to see?

"The package scap-security-guide-0.1.40-12 contains the file /usr/share/scap-security-guide/ansible/ssg-rhel7-role-C2S.yml. 

This Ansible playbook contains two tasks that insert errors into the /etc/audit/auditd.conf file:

On line 2756, the task "Configure auditd Max Log File Size" is missing an "=" in the line it inserts for "max_log_file".

On line 2841, the task "Configure auditd max_log_file_action Upon Reaching Maximum Log Size" is missing an "=" in the line it inserts for "max_log_file_action".

In fact, this typo appears to be present in several of the playbooks in that folder.

This causes us difficulty in using the provided ansible fix playbooks because we have to use --skip-tasks to disable these fixes."

Thanks to Bryan Parry from Red Hat for originally reporting this issue.

Moving out of Satellite6 as scap-security-guide comes from rhel repos.

Hello, thank you for filing this issue, moving to scap-security-guide component.

This bug should already be fixed in upstream SSG 0.1.41.
https://github.com/ComplianceAsCode/content/pull/3270

(In reply to Watson Yuuma Sato from comment #5)
> Hello, thank you for filing this issue, moving to scap-security-guide
> component.
> 
> This bug should already be fixed in upstream SSG 0.1.41.
> https://github.com/ComplianceAsCode/content/pull/3270

Thank you for providing the link to upstream!

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:2198