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:
SCAP Workbench let's the users customize (also called tailor) security content and then run a scan. After the scan the user gets back and ARF. The user could use `oscap xccdf generate fix --template <template> --result-id <ID> arf.xml` on the arf to get remediations but this is fairly hard to discover in the GUI. Instead SCAP Workbench should offer an option to save remediations for the machine that was scanned as ansible playbook or bash remediations.

Version-Release number of selected component (if applicable):
scap-workbench-1.1.4-5.el7

PR providing this functionality merged in upstream: https://github.com/OpenSCAP/scap-workbench/pull/143

I have verified that for scap-workbench-1.1.6-1.el7.x86_64, these scenarios work:
1. generate remediation from profile
2. generate remediation from customized profile
3. generate remediation from profile results

What does not work:
4. generate remediation from customized profile results

Even though description of this but is explicitly asking for the 4th scenario, we have decided to change scope.

There are bugzillas relevant to this feature:
Bug 1533108 (Generation of result-based remediation roles does not work for tailored profiles.)
Bug 1536885 (scap-workbench blindly allows generation of empty remediations)

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/RHEA-2018:1008