Elasticsearch Operator upgrade is stuck `timed out waiting for node to rollout` in RHOCP 4
Issue
-
The upgrade to Red Hat Elasticsearch Operator 5.8.13 is stuck
timed out waiting for node to rollout
:2024-10-27T12:31:25.500535646Z {"_ts":"2024-10-27T12:31:25.50046439Z","_level":"0","_component":"elasticsearch-operator_controllers_Elasticsearch","_message":"unable to update node","_error":{"msg":"timed out waiting for node to rollout","node":"elasticsearch-cdm-apmko5qx-1"},"cluster":"elasticsearch","namespace":"openshift-logging"} 2024-10-27T12:31:56.116689158Z {"_ts":"2024-10-27T12:31:56.116614221Z","_level":"0","_component":"elasticsearch-operator_controllers_Elasticsearch","_message":"unable to update node","_error":{"msg":"timed out waiting for node to rollout","node":"elasticsearch-cdm-apmko5qx-1"},"cluster":"elasticsearch","namespace":"openshift-logging"}
-
The Elasticsearch cluster remains in Yellow after several hours rolling out to the Red Hat Elasticsearch Operator 5.8.13
- The Elasticsearch CR status shows that
upgradePhase: preparationComplete
, but it's stuck not progressing in the upgrade returningtimed out waiting for node to rollout
, but the Elasticsearch pod is up and running
Environment
- Red Hat OpenShift Container Platform (RHOCP)
- 4
- Red Hat OpenShift Logging (RHOL)
- 5.8.13
- Red Hat Elasticsearch Operator
- Elasticsearch
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.