Bug 1686005

Summary: DISA openscap remediation playbook failing on correcting file permissions with RPM.
Product: Red Hat Enterprise Linux 7 Reporter: Abhijeet Joshi <abjoshi>
Component: scap-security-guideAssignee: Watson Yuuma Sato <wsato>
Status: CLOSED ERRATA QA Contact: Jan Černý <jcerny>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.6CC: janarula, jcerny, ktordeur, mhaicman, mmarhefk, openscap-maint
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: scap-security-guide-0.1.43-2.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-08-06 13:04:20 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Comment 2 Watson Yuuma Sato 2019-03-19 10:57:37 UTC
This has been fixed by https://github.com/ComplianceAsCode/content/pull/3328.
And further updated by https://github.com/ComplianceAsCode/content/pull/3341 and https://github.com/ComplianceAsCode/content/pull/3598.

In scap-security-guide-0.1.43 the playbook doesn't fail anymore.

Comment 4 Watson Yuuma Sato 2019-03-19 16:01:13 UTC
This patch is also required to fix a bug with rpm command using --setperms with --quiet.
https://github.com/ComplianceAsCode/content/pull/4205

Comment 7 Watson Yuuma Sato 2019-05-07 10:51:42 UTC
*** Bug 1662180 has been marked as a duplicate of this bug. ***

Comment 9 Jan Černý 2019-05-14 14:50:44 UTC
We need to update the upstream test suite because one of the test scenarios for this rule is currently broken. A fix of test suite is proposed to upstream in https://github.com/ComplianceAsCode/content/pull/4344

Comment 12 errata-xmlrpc 2019-08-06 13:04:20 UTC
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