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.
Bug 1578907 - SCAP Workbench fails to generate remediation role from a scan with custom profile
Summary: SCAP Workbench fails to generate remediation role from a scan with custom pro...
Keywords:
Status: CLOSED DUPLICATE of bug 1533108
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: scap-workbench
Version: 7.5
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Matěj Týč
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-05-16 15:14 UTC by Ryan Mullett
Modified: 2019-06-19 21:08 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-05-16 15:57:12 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Ryan Mullett 2018-05-16 15:14:50 UTC
Description of problem:

SCAP Workbench fails to generate remediation if you try to generate the remediation role from a scan using a custom profile. This is true for all profiles except for DISA STIG for Red Hat Enterprise Linux 7. The DISA STIG for Red Hat Enterprise Linux 7 appears to be the only profile that actually allows you to properly generate a remediation role from a scan using a customization.

Version-Release number of selected component (if applicable):
- RHEL 7.X, confirmed this is an issue on a fully updated RHEL 7.5 system

How reproducible:
- Always

Steps to Reproduce:
1. select any profile except for DISA STIG
2. click the "customize" button and make no changes, just click ok and save your customization profile
3. click "SCAN" and scan with the custom profile
4. click "Generate Remediation Role" and select any of the options (Bash, Ansible, Puppet)

Actual results:
-Failure with the following error message:

Error generating remediation role '/usr/share/xml/scap/ssg/content/remediation-test.yml': Exit code of 'oscap' was 1: OpenSCAP Error: Could not find Profile/@id="xccdf_org.ssgproject.content_profile_C2S_customized" to build policy from TestResult/@id="" [xccdf_session.c:1733]

Expected results:
- Expected that you would be able to generate a remediation role with a custom profile after scanning. 

Additional info:
- You can generate a remediation role from the custom profile, but not from the scan when using custom profile.

Comment 2 Marek Haicman 2018-05-16 15:57:12 UTC
Hello, thank you for the report. I haven't been able to reproduce the special case of DISA STIG profile - it fails every time for me.

Thus I consider it a duplicate of known Bug 1533108

*** This bug has been marked as a duplicate of bug 1533108 ***


Note You need to log in before you can comment on or make changes to this bug.