-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
failed to save outputs: Get <URL> unexpected EOF #3522
Comments
Someone should probably investigate to see if it is similar to K8S Executor bug and see if it is fragile and needs retries. |
Today I got a somehow different message, same scenario though: |
Hi
Additionally this retry potentially can cause steps which fail from business reasons. |
a retry is not possible on our case. I think I was able to solve this by using kubelet executor instead of k8sapi executor. But I still have to test if that really solves the problem. |
@lueenavarro i believe 'docker' is default executor ? |
Checklist:
What happened:
I have a pod that runs for about 4 hours. Then exits. The program exits after 4 hours as it should but the pod's status is ERROR. From the logs, it says "failed to save outputs: Get https://172.21.0.1:443/api/v1/namespaces/default/pods/nrsa-daily-schedule-nrl7m-2508837627: unexpected EOF"
What you expected to happen:
The pod's status should be SUCCESS.
How to reproduce it (as minimally and precisely as possible):
Run a pod that run for about 4 hours.
Anything else we need to know?:
Environment:
$ kubectl version -o yaml
Other debugging information (if applicable):
kubectl logs -c init
kubectl logs -c wait
kubectl logs -n argo $(kubectl get pods -l app=workflow-controller -n argo -o name)
Logs
YAML
task:
template:
Message from the maintainers:
If you are impacted by this bug please add a 👍 reaction to this issue! We often sort issues this way to know what to prioritize.
The text was updated successfully, but these errors were encountered: