Bug 1845964 - Elasticsearch upgrade from 4.4 to 4.5 fails because of disabled transient shard allocation
Summary: Elasticsearch upgrade from 4.4 to 4.5 fails because of disabled transient sha...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Logging
Version: 4.5
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
: 4.5.0
Assignee: Jeff Cantrill
QA Contact: Anping Li
URL:
Whiteboard:
Depends On: 1846316
Blocks: 1845118
TreeView+ depends on / blocked
 
Reported: 2020-06-10 13:44 UTC by OpenShift BugZilla Robot
Modified: 2020-07-13 17:44 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-07-13 17:43:50 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift elasticsearch-operator pull 393 0 None closed [release-4.5] Bug 1845964: Clear transient shard allocation setting before upgrade 2021-02-09 23:56:38 UTC
Red Hat Product Errata RHBA-2020:2409 0 None None None 2020-07-13 17:44:07 UTC

Description OpenShift BugZilla Robot 2020-06-10 13:44:31 UTC 
+++ This bug was initially created as a clone of Bug #1845711 +++

Description of problem:

Unable to complete upgrade because the security shard is not able to be allocated due to transient shard allocation setting:

"explanation" : "no allocations are allowed due to cluster setting [cluster.routing.allocation.enable=none]"
Comment 3 Anping Li 2020-06-11 11:24:06 UTC 
Blocked by OLM bug https://bugzilla.redhat.com/show_bug.cgi?id=1846316
Comment 4 Anping Li 2020-06-16 05:53:57 UTC 
Pass on clusterlogging.4.5.0-202006101338, clusterlogging.4.5.0-202006101338 and using workaround olm.skipRange: '>=4.4.0-0 <4.5.0-202006101717'
Comment 5 errata-xmlrpc 2020-07-13 17:43:50 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:2409
Note You need to log in before you can comment on or make changes to this bug.