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.

Description of problem:
Remove deprecated follow argument of replace module from Ansible remediations. The argument was deprecated in Ansible 2.5 and Ansible 2.10 completely removes it. This might cause that Ansible fixes from scap-security-guide which are still using the argument will fail.

Based on https://access.redhat.com/support/policy/updates/ansible-engine Ansible 2.10 is not yet supported, but this is to make sure that once it will be supported our Ansible playbooks won't have any issues with this new version.

Issue is already fixed in upstream: https://github.com/ComplianceAsCode/content/pull/6139


Version-Release number of selected component (if applicable):
scap-security-guide-0.1.49-13.el7


How reproducible:
always with ansible-2.10


Steps to Reproduce:
Run Ansible playbook of any profile containing one of the rules updated in the https://github.com/ComplianceAsCode/content/pull/6139


Actual results:
Ansible remediations which are still using follow argument are failing when using Ansible 2.10


Expected results:
Ansible remediations from scap-security-guide are no longer using follow argument and are working properly with Ansible 2.10


Additional info:

Fixed upstream in this PR:
https://github.com/ComplianceAsCode/content/pull/6139

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 (scap-security-guide bug fix and enhancement update), 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-2021:1383