You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 4, 2023. It is now read-only.
Cluster was upgrade from 6.2.3 to 6.2.4. Master node pool was upgraded then data pool started. 3 of the 5 data pods were upgraded and then upgrade stopped.
What you expected to happen:
All pods were upgraded.
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
There were no errors in the controller manager logs and no events on the elasticsearch cluster resource. It just stopped executing the UpdateVersion action. This is with versions v0.1.0-alpha.1 of all components. It is stuck at partition 2 in the statefulset.
Is this a BUG REPORT or FEATURE REQUEST?:
/kind bug
What happened:
Cluster was upgrade from 6.2.3 to 6.2.4. Master node pool was upgraded then data pool started. 3 of the 5 data pods were upgraded and then upgrade stopped.
What you expected to happen:
All pods were upgraded.
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
There were no errors in the controller manager logs and no events on the elasticsearch cluster resource. It just stopped executing the UpdateVersion action. This is with versions v0.1.0-alpha.1 of all components. It is stuck at partition 2 in the statefulset.
Cluster configuration:
Environment:
kubectl version
):The text was updated successfully, but these errors were encountered: