Bug 1845993 - Elasticsearch operator sets shard allocation to "none" during restart for certs
Summary: Elasticsearch operator sets shard allocation to "none" during restart for certs
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Logging
Version: 4.4
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 4.4.z
Assignee: ewolinet
QA Contact: Giriyamma
URL:
Whiteboard:
Depends On: 1840909
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-06-10 14:39 UTC by ewolinet
Modified: 2020-06-23 00:57 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1840909
Environment:
Last Closed: 2020-06-23 00:57:53 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift elasticsearch-operator pull 394 0 None closed [release-4.4] Bug 1845993: Fix unnecessary restarts and harden rolling restarts 2020-11-17 08:04:55 UTC
Red Hat Product Errata RHBA-2020:2580 0 None None None 2020-06-23 00:57:59 UTC

Comment 4 Giriyamma 2020-06-17 11:21:59 UTC
Moving to verified, Elasticsearch operator is not setting the shard allocation to "none" during restart for certs.

$ oc exec -c elasticsearch elasticsearch-cdm-yt18aofm-1-7657bdbcc4-wfhqv -- es_util '--query=_cluster/settings?pretty'
{
  "persistent" : {
    "cluster" : {
      "routing" : {
        "allocation" : {
          "enable" : "all"
        }
      }
    },
    "discovery" : {
      "zen" : {
        "minimum_master_nodes" : "2"
      }
    }
  },
  "transient" : { }
}


$ oc get csv
NAME                                        DISPLAY                  VERSION              REPLACES                            PHASE
clusterlogging.4.4.0-202006160135           Cluster Logging          4.4.0-202006160135   clusterlogging.4.4.0-202006080610   Succeeded
elasticsearch-operator.4.4.0-202006111738   Elasticsearch Operator   4.4.0-202006111738                                       Succeeded

Comment 6 errata-xmlrpc 2020-06-23 00:57:53 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:2580


Note You need to log in before you can comment on or make changes to this bug.