This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
Bug 2129074 - SCAP Ansible playbooks not idempotent
Summary: SCAP Ansible playbooks not idempotent
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: scap-security-guide
Version: 9.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Vojtech Polasek
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-09-22 12:33 UTC by Marko Myllynen
Modified: 2023-08-09 15:10 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-08-09 15:10:54 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   RHEL-1101 0 None None None 2023-08-09 15:10:38 UTC
Red Hat Issue Tracker RHELPLAN-134692 0 None None None 2022-09-22 12:42:06 UTC

Description Marko Myllynen 2022-09-22 12:33:12 UTC 
Description of problem:
Ansible playbooks should be idempotent meaning that running them twice in a row the second run should do no changes. However, running e.g. the SCAP STIG playbook twice creates around hundred change for the second run. Ideally the second run would report no changes at all.
Comment 4 Matěj Týč 2023-08-09 14:53:23 UTC 
This BZ has been migrated to https://issues.redhat.com/browse/RHEL-1101 where the solution and discussion can continue.
Comment 5 RHEL Program Management 2023-08-09 15:10:54 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues.
Note You need to log in before you can comment on or make changes to this bug.