Bug 1845993

Summary: Elasticsearch operator sets shard allocation to "none" during restart for certs
Product: OpenShift Container Platform Reporter: ewolinet
Component: LoggingAssignee: ewolinet
Status: CLOSED ERRATA QA Contact: Giriyamma <gkarager>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.4CC: anli, aos-bugs, ploffay
Target Milestone: ---   
Target Release: 4.4.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1840909 Environment:
Last Closed: 2020-06-23 00:57:53 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: 1840909    
Bug Blocks:    

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