Bug 1793551

Summary: PROMTAIL_IMAGE doesn't exist in the CSV clusterlogging.4.3.0-202001081344
Product: OpenShift Container Platform Reporter: Anping Li <anli>
Component: LoggingAssignee: Jeff Cantrill <jcantril>
Status: CLOSED ERRATA QA Contact: Anping Li <anli>
Severity: low Docs Contact:
Priority: unspecified    
Version: 4.3.0CC: aos-bugs, jcantril, jokerman
Target Milestone: ---Flags: jcantril: needinfo-
Target Release: 4.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-07-13 17:13:17 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:
Bug Depends On: 1817592    
Bug Blocks:    

Description Anping Li 2020-01-21 14:43:59 UTC
Description of problem:
PROMTAIL_IMAGE is a dev-preview image which shouldn't be in the 4.3/cluster-logging.v4.3.0.clusterserviceversion.yaml

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

How reproducible:


Steps to Reproduce:
1. deploy cluster logging operators using redhat-operators-stage operator registry

oc get csv clusterlogging.4.3.0-202001081344 -o yaml |grep  PROMTAIL_IMAGE -A 1
                - name: PROMTAIL_IMAGE
                  value: registry.stage.redhat.io/openshift4/ose-promtail@sha256:1264aa92ebc6cccf46da3a35fbb54421b806dda5640c7e9706e6e815d13f509d



Actual results:
clusterlogging.4.3.0-202001081344 specified an image which will not be released.

Expected results:
Drop PROMTAIL_IMAGE
Use Upstream image quay.io/openshift/origin-promtail:latest

Additional info:

Comment 5 Anping Li 2020-05-15 13:50:30 UTC
Waiting csv bundles.

Comment 9 Anping Li 2020-05-22 03:06:01 UTC
Verified in clusterlogging.4.5.0-202005201941

Comment 12 Anping Li 2020-05-23 12:46:54 UTC
Verified in clusterlogging.4.5.0-202005221517

Comment 14 errata-xmlrpc 2020-07-13 17:13:17 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