Bug 1789261

Summary:	transient.cluster.routing.allocation.enable is none sometimes after cluster upgrade
Product:	OpenShift Container Platform	Reporter:	Anping Li <anli>
Component:	Logging	Assignee:	ewolinet
Status:	CLOSED ERRATA	QA Contact:	Anping Li <anli>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.2.0	CC:	aos-bugs, ewolinet, jcantril, rmeggins
Target Milestone:	---	Keywords:	Reopened
Target Release:	4.2.z
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1753568	Environment:
Last Closed:	2020-02-12 12:16:16 UTC	Type:	---
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:	1753568
Bug Blocks:	1761080

Comment 1 Anping Li 2020-01-09 08:32:55 UTC

Why I cloned this bug 4.2?  We still hit this issue when upgrade from 4.2 to 4.3.  
The fix is in EO 4.3. But during upgrade,  CLO was upgraded prior to EO, we still may hit this error (At that point EO is still 4.2, without the fix).  I suggest backporting fix to EO 4.2

Comment 5 Anping Li 2020-02-06 08:03:40 UTC

Verified in Elasticsearch Operator:4.3.1-202002032140

Comment 7 errata-xmlrpc 2020-02-12 12:16:16 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:0395