Hide Forgot
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]"
Blocked by an OLM bug https://bugzilla.redhat.com/show_bug.cgi?id=1846316 when upgrading from Logging 4.4 to 4.5 on OCP 4.5. I am trying to see if we can overcome it by an OCP 4.4 to 4.5 cluster upgrade.
$ oc exec elasticsearch-cdm-vx0f1dvs-1-76ddbb85b4-nvd4j -- es_util --query=_cluster/settings |jq Defaulting container name to elasticsearch. Use 'oc describe pod/elasticsearch-cdm-vx0f1dvs-1-76ddbb85b4-nvd4j -n openshift-logging' to see all of the containers in this pod. { "persistent": { "cluster": { "routing": { "allocation": { "enable": "all" } } }, "discovery": { "zen": { "minimum_master_nodes": "2" } } }, "transient": {} } Verified with quay.io/openshift/origin-elasticsearch-operator@sha256:65dfb97c1b787f53860455fbc6595a6b3211e30b564e04b84dde70ab125aa00d.
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.6 GA Images), 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:4196