Bug 1381717
Summary: | atomic scan failed if a system container image exists | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Qian Cai <qcai> |
Component: | atomic | Assignee: | Giuseppe Scrivano <gscrivan> |
Status: | CLOSED ERRATA | QA Contact: | atomic-bugs <atomic-bugs> |
Severity: | high | Docs Contact: | Yoana Ruseva <yruseva> |
Priority: | high | ||
Version: | 7.3 | CC: | ajia, dwalsh, gscrivan, yruseva |
Target Milestone: | rc | Keywords: | Extras |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Known Issue | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-12-06 17:42: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
Qian Cai
2016-10-04 19:53:43 UTC
Giuseppe any idea why this is failing on system containers? I have just opened a PR upstream to address this issue: https://github.com/projectatomic/atomic/pull/680 I have merged that fix. Lets mark this as fixed in atomic-1.13 It works well in atomic-1.13.1-2 and atomic-1.13.6-1, so moving the bug to VERIFIED status. 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-2857.html |