Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1741753

Summary: cluster-logging-operator image size is too small 52.4 kB
Product: OpenShift Container Platform Reporter: Anping Li <anli>
Component: ReleaseAssignee: Luke Meyer <lmeyer>
Status: CLOSED ERRATA QA Contact: Wei Sun <wsun>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.1.zCC: aos-bugs, jokerman, vlaad
Target Milestone: ---Keywords: Regression, TestBlocker
Target Release: 4.1.z   
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: 2019-08-28 19:55:01 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 Anping Li 2019-08-16 05:29:54 UTC 
Description of problem:


The openshift/ose-cluster-logging-operator image size is only 52.4 kB. It need to be rebuild.

openshift/ose-cluster-logging-operator:v4.1.12-201908150609   2515b05f515c        10 hours ago        52.4 kB

Version-Release number of selected component (if applicable):
openshift/ose-cluster-logging-operator:v4.1.12-201908150609


How reproducible:
always

Steps to Reproduce:
1. deploy cluster logging using redhat-operators-art (The version is v4.1.12-201908150609 currently)
2. check the cluster-logging-operator status
$ oc get pods
NAME                                        READY   STATUS                 RESTARTS   AGE
cluster-logging-operator-749cbcc6b7-2k7gm   0/1     CreateContainerError   0          25m

3. check the openshift/ose-cluster-logging-operator image size
it is 52.4 kB


Actual results:
The clusterlogging operator pod couldn't be started. 


Expected results:

The cluster-logging-operator can be started.

Additional info:
Comment 7 errata-xmlrpc 2019-08-28 19:55:01 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-2019:2547