argo-rollouts: status command exits before timout
Summary
I have a rollout that was being watched via status
with a --timeout=3h
flag. It exited with a degraded
after 20 minutes.
Diagnostics
What version of Argo Rollouts are you running? v1.0.1 (kubectl-argo-rollouts = v1.0.0)
2021-05-27 14:13:33 EDT Status: Downloaded newer image for gcr.io/helpful-cat-109717/kubectl-argo-rollouts:v1.0.0
2021-05-27 14:13:34 EDT Executing command: kubectl get deployment -l "app.kubernetes.io/name=managed-satellite-envoy" -o name | cut -d '/' -f 2 | xargs -n 1 kubectl-argo-rollouts status --timeout=3h
2021-05-27 14:33:51 EDT Error: The rollout is in a degraded state with message: ProgressDeadlineExceeded: ReplicaSet "public-satellite-pools-managed-satellite-envoy-v2-6f9df7c4bf" has timed out progressing.
14:13 is when helm pushed the change. 14:33 is when the command failed.
The rollout itself completed successfully shortly thereafter.
(there is only one rollout returned by the first kubectl, and I’ve omitted the extra flags to kubectl for brevity)
# Paste the logs from the rollout controller
Logs attached. The server doesn't show any errors. Possibly this is a client bug. I've seen this happen twice now. Is there anything else I can provide to help here?
# Logs for the entire controller:
kubectl logs -n argo-rollouts depl
[filtered2.csv](https://github.com/argoproj/argo-rollouts/files/6556579/filtered2.csv)
oyment/argo-rollouts
# Logs for a specific rollout:
kubectl logs -n argo-rollouts deployment/argo-rollouts | grep rollout=<ROLLOUTNAME>
Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritize the issues with the most 👍.
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 15 (7 by maintainers)
I can confirm that setting
progressDeadlineSeconds
to1200
fixed my issue.