If applicable, add screenshots to help explain your problem.
Do you have any additional context?
If I do step 2 above and wait for the OpenSearch cluster to complete getting created (i.e. the 3 nodes come to a running state and the cluster health is green) and then do step 3 (add ISM policy), the panic does not happen.
But if I do step 3 immediately after step 2, then the operator panics and crashes several times and.
However, when using deployment pipelines, we cannot control the delay between resources
What is the bug?
When adding an
OpenSearchISMPolicy
while the OpenSearch cluster is getting created, the controller panics resulting in a container crashThe operator pod will crash several times and then continue running.
How can one reproduce the bug?
Install the operator
Create an OpenSearch cluster using
kubectl apply
. This is the cluster definition I usedApply the following ISM policy using
kubectl apply
At this point, the operator pod would exit with an error
What is the expected behavior?
EXpected the ISM Policy to be added without an issue
What is your host/environment?
Kubernetes 1.25 OpenSearch 2.11.1 OpenSearch operator 2.6.0
Do you have any screenshots?
If applicable, add screenshots to help explain your problem.
Do you have any additional context?
If I do step 2 above and wait for the OpenSearch cluster to complete getting created (i.e. the 3 nodes come to a running state and the cluster health is green) and then do step 3 (add ISM policy), the panic does not happen. But if I do step 3 immediately after step 2, then the operator panics and crashes several times and.
However, when using deployment pipelines, we cannot control the delay between resources