rameshar16

I am also facing the similar issue with 2.7.0.

Added the below config and did nnot notice any issue during the deployment. ``` - name: "warm" actions: - allocation: require: "temp: warm" include: "" exclude: "" waitFor: "1m" transitions:...

Hi @prudhvigodithi , I did not see any see after I added the below data for allocation along with the require field. include: "" exclude: "" waitFor: "1m" Below is...

I did not see any error during the deployment with above configurations, but the ISM Polices did not create with the below configs. # - allocation: # require: "temp: warm"...

I am getting the below error with below config. - name: "hot" actions: - allocation: require: temp: "hot" include: {} exclude: {} waitFor: "1m" transitions: - stateName: "warm" conditions: minIndexAge:...

`>helm diff upgrade opensearch-cr ./charts/opensearch-cluster/ --values ./charts/opensearch-cluster/values.yaml -n opensearch apiVersion: opensearch.opster.io/v1 kind: OpenSearchCluster metadata: name: opensearch-cr namespace: opensearch spec: general: **- version: 2.4.0 + version: 2.6.0** httpPort: 9200 vendor: opensearch...

``` >k get po -n opensearch -w NAME READY STATUS RESTARTS AGE opensearch-cr-coordinators-0 1/1 Running 0 17h opensearch-cr-coordinators-1 1/1 Running 0 16h opensearch-cr-coordinators-2 1/1 Running 0 16h opensearch-cr-dashboards-54d6ccb67c-nw9sp 1/1 Running...

Hi Team, I am using the OpenSearch Operator 2.7.0. I am also facing the similar issue. Thanks,