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

Bug 1809498

Summary:	Failed to upgrade logging from 4.4 to 4.5 - upgrading EO firstly
Product:	OpenShift Container Platform	Reporter:	Qiaoling Tang <qitang>
Component:	Logging	Assignee:	Jeff Cantrill <jcantril>
Status:	CLOSED ERRATA	QA Contact:	Anping Li <anli>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	4.5	CC:	anli, aos-bugs, jcantril, mburke
Target Milestone:	---
Target Release:	4.5.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:
Clones:	1826781 (view as bug list)		Environment:
Last Closed:	2020-08-04 18:03: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:
Embargoed:
Bug Depends On:
Bug Blocks:	1825056, 1829064

Comment 1 Jeff Cantrill 2020-03-03 11:28:32 UTC

We are likely still awaiting proper images from ART since this is trying to boot an ES5 node.  ES6 will be used in 4.5.  What images does the EO say it should be using?  What images does the CLO say it should be using?

Comment 2 Anping Li 2020-03-10 03:04:39 UTC

Yes, there isn't 4.5 channel in operator-registry redhat-operatrors-art. Waiting art.

Comment 3 Jeff Cantrill 2020-04-14 20:08:20 UTC

Please retest now there are available images for 4.5. One suspicion I have is if you upgrade CLO before EO that records will be written to an index with a '-write' suffix and thus the new indexmanagement will be broken

Comment 5 Jeff Cantrill 2020-05-04 18:16:46 UTC

This blocks 4.4 to 4.5 upgrade because:

* EO tries to rollout ES6 cluster using ES6 config
* EO uses the image specified by CLO which is still on ES5
* The ES5 image is unable to start with ES6 config

Comment 6 Jeff Cantrill 2020-05-04 19:36:17 UTC

The operator additionally is not upgrading the proxy container to support the elasticsearch-proxy

Comment 9 Anping Li 2020-05-15 12:52:31 UTC

Upgrade Pass.  But kibana couldn't be automated migrated (Bug 1832849)

Comment 11 errata-xmlrpc 2020-08-04 18:03: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 (OpenShift Container Platform 4.5 image release 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