Bug 1346921
Summary: | temp file in /etc/atomic.d/ causes an error when running 'atomic scan' | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Micah Abbott <miabbott> |
Component: | atomic | Assignee: | Brent Baude <bbaude> |
Status: | CLOSED ERRATA | QA Contact: | atomic-bugs <atomic-bugs> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 7.2 | CC: | ajia, dwalsh |
Target Milestone: | rc | Keywords: | Extras |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-11-04 09:06:16 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: | |
Embargoed: |
Description
Micah Abbott
2016-06-15 16:15:05 UTC
Could you run this with atomic --debug scan registry.access.redhat.com/rhel7 Upstream merge request -> https://github.com/projectatomic/atomic/pull/565 should remedy this. Brent's PR fixed the handling of bad data in /etc/atomic.d So I think this will be fixed in atomic 1.12 Fixed in atomic-1.12 Only print an error message but do not fail in atomic-1.12.0-1.el7.x86_64, so moving to VERIFIED status. # atomic scan --scanner openscap --scan_type cve registry.access.redhat.com/rhel7:latest Error: Unable to load scannerfile /etc/atomic.d/.openscap.swp. Continuing... Error: Unable to load scannerfile /etc/atomic.d/.openscap.swp. Continuing... docker run -t --rm -v /etc/localtime:/etc/localtime -v /run/atomic/2016-09-18-12-11-40-493238:/scanin -v /var/lib/atomic/openscap/2016-09-18-12-11-40-493238:/scanout:rw,Z -v /etc/oscapd:/etc/oscapd:ro rhel7/openscap oscapd-evaluate scan --no-standard-compliance --targets chroots-in-dir:///scanin --output /scanout <ignore .../> 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://rhn.redhat.com/errata/RHBA-2016-2628.html |