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 1257592 - Don't exit with traceback if provided XCCDF / DS benchmark contains dangling selector
Summary: Don't exit with traceback if provided XCCDF / DS benchmark contains dangling ...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: oscap-anaconda-addon
Version: 7.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Vratislav Podzimek
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-08-27 12:16 UTC by Jan Lieskovsky
Modified: 2016-02-05 14:26 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-02-05 14:26:05 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Jan Lieskovsky 2015-08-27 12:16:25 UTC 
Description of problem:

Oscap Anaconda Add-on currently exits with traceback in the scenario when some profile in the provided XCCDF / DataStream benchmark references a non-existing XCCDF rule (dangling selector).

While it's true, the issue should be caught sooner (the scanner should identify such a situation, and refuse to proceed further. The content shouldn't reference un-implemented rules), there's a use case with the tailoring benchmark example yet (though SCAP content being valid in default settings, after tailoring it's possible to create a profile containing un-implemented rules).

Therefore OAA should more gracefully handle this situation. Upstream openscap bug is here:
  [1] https://fedorahosted.org/openscap/ticket/474

Once the openscap scanner is able properly to handle this situation, OAA should display relevant openscap message in some OAA dialog (rather than fail with traceback).

How reproducible:
Always

Steps to Reproduce:
1. Provide XCCDF / DS benchmark to OAA having profile containing referenced, but un-implemented XCCDF rule
2. Start the Anaconda install (load the SCAP content etc.)

Actual results:
Anaconda traceback.

Expected results:
Anaconda displays an error dialog reporting there's missing rule definition in the benchmark (the error message provided by oscap is propagated to Anaconda UI), and ask the user to provide different SCAP content.
Comment 1 Jiri Kortus 2016-02-05 14:22:28 UTC 
I'm not able to reproduce this bug on RHEL-7.2, it seems that it has been fixed, probably with fix for bug #1247654 which is very similar to this one and presumably resulted in the same traceback.

When an invalid security content is used (even the content in the upstream bug referenced in bug description), no traceback occurs and an error message is displayed.
Comment 2 RHEL Program Management 2016-02-05 14:26:05 UTC 
Quality Engineering Management has reviewed and declined this request.
You may appeal this decision by reopening this request.
Note You need to log in before you can comment on or make changes to this bug.