Bug 1706509

Summary: should not use the upstream image for clusterlogging operator
Product: OpenShift Container Platform Reporter: Anping Li <anli>
Component: ReleaseAssignee: Jeff Cantrill <jcantril>
Status: CLOSED ERRATA QA Contact: Anping Li <anli>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.1.0CC: aos-bugs, jcantril, jokerman, mmccomas, rmeggins, smunilla, sponnaga, tbielawa, vlaad, wsun
Target Milestone: ---   
Target Release: 4.1.0   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-06-04 10:48:23 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:
Description Flags
Community Operator none

Description Anping Li 2019-05-05 06:54:48 UTC
Description of problem:
The clusterlogging operator should use downstream image

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

How reproducible:

Steps to Reproduce:
1. Deploy clusterlogging
2. Check the image

Actual results:
Tghe clusterlogging operator is using upstream image

Expected results:

It should use downstream image.

Additional info:

Comment 4 Anping Li 2019-05-07 02:51:38 UTC
Created attachment 1564943 [details]
Community Operator

Comment 5 Anping Li 2019-05-07 02:56:44 UTC
The market place provide clusterlogging as community operator. The use downstream imagfe, Could you confirm when the clusterlogging are provided as RHEL Operators?

Comment 7 Anping Li 2019-05-08 02:02:06 UTC
@jeff What image tags will be used for all cluster logging images? the latest,v4.1 or manifest?

Comment 8 Anping Li 2019-05-08 02:34:10 UTC
it is using tag with timestamp  v4.1.0-201905070632

Comment 11 errata-xmlrpc 2019-06-04 10:48:23 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.