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 Jan 12, 2022. It is now read-only.
During an upgrade to version v2010.08.13, the Cortex ingester Statefulset was marked ready, but the rollout was still in progress. The CLI exited with success, and the rollout continued in the background.
Here is the message printed by the CLI when waiting for the deployments to finish:
2021-08-17T15:11:33.168Z info: waiting for 1 StatefulSets
2021-08-17T15:11:33.168Z debug: Waiting for 1 pods to be ready for StatefulSet cortex/ingester
2021-08-17T15:11:33.169Z info: waiting for 0 Certificates
2021-08-17T15:11:38.170Z info: waiting for 0 Deployments
2021-08-17T15:11:38.170Z info: waiting for 0 DaemonSets
2021-08-17T15:11:38.171Z info: waiting for 1 StatefulSets
2021-08-17T15:11:38.171Z debug: Waiting for 1 pods to be ready for StatefulSet cortex/ingester
2021-08-17T15:11:38.171Z info: waiting for 0 Certificates
2021-08-17T15:11:43.172Z info: waiting for 0 Deployments
2021-08-17T15:11:43.172Z info: waiting for 0 DaemonSets
2021-08-17T15:11:43.172Z info: waiting for 0 StatefulSets
2021-08-17T15:11:43.172Z info: waiting for 0 Certificates
2021-08-17T15:11:43.173Z info: waiting for expected HTTP responses at these URLs: {
This is the ingester Statefulset spec, notice the 5 replicas:
This bug occurred in an Opstrace instance with 5 ingesters. When it finished the rollout of ingester-2, the Statefulset was marked ready, but it was still missing ingester-1 and 0 since 3 and 4 had already completed the rollout.
Describe the bug
During an upgrade to version v2010.08.13, the Cortex ingester Statefulset was marked ready, but the rollout was still in progress. The CLI exited with success, and the rollout continued in the background.
Here is the message printed by the CLI when waiting for the deployments to finish:
This is the ingester Statefulset spec, notice the 5 replicas:
To Reproduce
This bug occurred in an Opstrace instance with 5 ingesters. When it finished the rollout of ingester-2, the Statefulset was marked ready, but it was still missing ingester-1 and 0 since 3 and 4 had already completed the rollout.
Expected behavior
The CLI Statefulset readiness check should wait for all pods to be ready.
The text was updated successfully, but these errors were encountered: