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