Bug 1882495

Summary: The new index isn't correct after upgrading logging from 4.4 to 4.5
Product: OpenShift Container Platform Reporter: Jeff Cantrill <jcantril>
Component: LoggingAssignee: Jeff Cantrill <jcantril>
Status: CLOSED ERRATA QA Contact: Anping Li <anli>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.4CC: aos-bugs, jcantril, periklis, qitang
Target Milestone: ---   
Target Release: 4.4.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: logging-exploration
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Cause: pre 4.5 ES clusters can end up in a state which will block proper 4.5 logging because the indexmanagement is in the incorrect state Consequence: indices get created with the name of the intended alias Fix: Block auto creation of "-write" suffix indices Result: This will block 4.5 forwarders from putting 4.4 stores in a bad state
Story Points: ---
Clone Of: 1809511 Environment:
Last Closed: 2020-11-11 01:08:01 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: 1809511, 1827032    
Bug Blocks:    

Comment 2 Anping Li 2020-10-20 04:43:51 UTC
Verified on elasticsearch-operator.4.4.0-202010151519.p0,clusterlogging.4.4.0-202010151519.p0

Comment 5 errata-xmlrpc 2020-11-11 01:08:01 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.4.30 extras update), 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:4323