Bug 1665824

Summary:	No image quay.io/openshift/cluster-logging-operator:latest and quay.io/openshift/elasticsearch-operator:latest
Product:	OpenShift Container Platform	Reporter:	Anping Li <anli>
Component:	Logging	Assignee:	Jeff Cantrill <jcantril>
Status:	CLOSED ERRATA	QA Contact:	Anping Li <anli>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.1.0	CC:	aos-bugs, jcantril, rmeggins
Target Milestone:	---
Target Release:	4.1.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:	undefined	Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-06-04 10:41:55 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-01-14 08:12:21 UTC

Description of problem:
By default, the image name is quay.io/openshift/cluster-logging-operator:latest. But the image name is quay.io/openshift/origin-cluster-logging-operator:latest

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

How reproducible:
Alway

Steps to Reproduce:
1. deploy logging via OLM
2.
3.

Actual results:
The cluster-logging and elasticsearch operator couldn't be started.


Expected results:
The cluster-logging and elasticsearch operator can be started.

Additional info:

Comment 1 Anping Li 2019-01-14 08:14:25 UTC

@jeff Please assign to the ART team if the image should be retagged by them.

Comment 2 Anping Li 2019-01-14 09:27:36 UTC

The workaround as below:
1) oc edit csv -n openshift-logging, add origin- to the operator images
 quay.io/openshift/origin-cluster-logging-operator:latest
 quay.io/openshift/origin-elasticsearch-operator:latest

 
2) delete the operator deployment
  oc delete deployment cluster-logging-operator
  oc delete deployment elasticsearch-operator

Comment 5 errata-xmlrpc 2019-06-04 10:41:55 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:0758