Bug 1823683 - The container security operator did not work well on console
Summary: The container security operator did not work well on console
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: ISV Operators
Version: 4.5
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 4.5.0
Assignee: Matt Dorn
QA Contact: Bruno Andrade
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-04-14 09:20 UTC by shahan
Modified: 2020-07-13 17:27 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-07-13 17:27:24 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:2409 0 None None None 2020-07-13 17:27:47 UTC

Description shahan 2020-04-14 09:20:07 UTC
Description of problem:
The container security operator did not work well on console. It cannot scan out the pod which are using images with vulnerabilities

Version-Release number of selected component (if applicable):

4.5.0-0.nightly-2020-04-13-213244
How reproducible:

Always
Steps to Reproduce:
1. install the  container security operator via operatorhub
2. create pod using image on quay with vulnerabilities, such as 
quay.io/repository/bitnami/redis/manifest/sha256:c51f9b027d358a07b7201e37163e0fabb12b1ac06a640ab1a84a78f541e6c3fa?tab=vulnerabilities
3.

Actual results:
The container security did not scan out the vulnerabilities in the pod image.
$oc get ImageManifestVuln  -n openshift-operators
No resources found

$ oc logs -f container-security-operator-779bf58cdb-7898w | grep vulhigh22
.....
E0414 09:09:56.455790       1 labeller.go:191] yapei/vulhigh22-7459dbfdc5-lf27l failed with : &{%!w(string=Pod phase not running: Pending)}
level=info msg="Requeued item" key=yapei/vulhigh22-7459dbfdc5-lf27l
E0414 09:09:56.580302       1 labeller.go:191] yapei/vulhigh22-7459dbfdc5-lf27l failed with : &{%!w(string=Pod phase not running: Pending)}
level=info msg="Requeued item" key=yapei/vulhigh22-7459dbfdc5-lf27l
E0414 09:10:01.700591       1 labeller.go:191] yapei/vulhigh22-7459dbfdc5-lf27l failed with : &{%!w(string=Pod phase not running: Pending)}
level=info msg="Requeued item" key=yapei/vulhigh22-7459dbfdc5-lf27l
level=debug msg="Pod updated" key=yapei/vulhigh22-7459dbfdc5-lf27l
level=info msg="Garbage collecting unreferenced ImageManifestVulns" key=yapei/vulhigh22-7459dbfdc5-lf27l
level=error msg="Failed to sync layer data" key=yapei/vulhigh22-7459dbfdc5-lf27l err="json: cannot unmarshal bool into Go struct field AppCapabilities.capabilities of type string"
level=info msg="Garbage collecting unreferenced ImageManifestVulns" key=yapei/vulhigh22-7459dbfdc5-lf27l
level=error msg="Failed to sync layer data" key=yapei/vulhigh22-7459dbfdc5-lf27l err="json: cannot unmarshal bool into Go struct field AppCapabilities.capabilities of type string"

Expected results:
The container security should scan out the vulnerabilities in the pod image and create the ImageManifestVuln

Additional info:

Comment 4 errata-xmlrpc 2020-07-13 17:27:24 UTC
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-2020:2409


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