-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
Pod not found when resubmit --memoized #3214
Labels
Comments
This was referenced Jun 22, 2020
Investigating. Sorry about the delay. |
I think this is a bug with panics |
Related? #2721 |
See #2385 |
Related #1552 |
6 tasks
See #3097 |
6 tasks
OK. So @sarabala1979 fixed on master - but now we need to back-port a new fix to v2.9. |
6 tasks
alexec
added a commit
that referenced
this issue
Jul 13, 2020
alexec
added a commit
that referenced
this issue
Jul 13, 2020
alexec
added a commit
to alexec/argo-workflows
that referenced
this issue
Jul 13, 2020
6 tasks
alexec
added a commit
that referenced
this issue
Jul 13, 2020
alexec
added a commit
that referenced
this issue
Jul 13, 2020
alexec
added a commit
that referenced
this issue
Jul 14, 2020
Fixed in v2.9 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
What happened:
Using the
resubmit --memoized
example, the resubmitted workflow fails with a "pod deleted" message in the place of the original pod that failed. See "workflow results" below.What you expected to happen:
I expected that pod to be retried.
How to reproduce it (as minimally and precisely as possible):
Using the example of https://github.com/argoproj/argo/blob/master/examples/resubmit.yaml then issuing resubmit with
$ argo resubmit --watch --memoized <workflow>
Anything else we need to know?:
Tried on local Kubernetes and GKE.
Environment:
Other debugging information (if applicable):
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: