| Summary: | scap-workbench does not expect --fetch-remote-resources warning | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Marek Haicman <mhaicman> |
| Component: | scap-workbench | Assignee: | Watson Yuuma Sato <wsato> |
| Status: | CLOSED ERRATA | QA Contact: | Marek Haicman <mhaicman> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 7.3 | CC: | gkonda, mhaicman, openscap-maint |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | scap-workbench-1.1.4-4.el7 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-08-01 09:09:29 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: | |
|
Description
Marek Haicman
2016-08-17 19:51:15 UTC
Fixed upstream in https://github.com/OpenSCAP/scap-workbench/pull/82 and https://github.com/OpenSCAP/openscap/pull/540 Verified fix on version: [dahaic@localhost ~]$ rpm -qa scap-workbench scap-workbench-1.1.4-4.el7.x86_64 [dahaic@localhost ~]$ rpm -qa openscap-scanner openscap-scanner-1.2.14-2.el7.x86_64 When scanning profile with remote resources requirement, diagnosis window now shows no error, and these two warnings: 13:37:50 warning Remote resources might be necessary for this profile to work properly. Please select "Fetch remote resources" for complete scan 13:37:50 warning Skipping https://www.redhat.com/security/data/oval/com.redhat.rhsa-RHEL7.xml.bz2 file which is referenced from XCCDF content When fetch remote resources is checked, it currently fails, depending on scap-security-guide version. It is a regression, but not due to update of scap-workbench, but because of ssg. So created a new Bug 1456429 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-2017:2296 |