-
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
Argo event generate workflow name using epoch time cause duplicate name. #6732
Labels
Comments
alexec
added
solution/workaround
There's a workaround, might not be great, but exists
invalid
labels
Sep 21, 2021
alexec
added
wontfix
and removed
solution/workaround
There's a workaround, might not be great, but exists
invalid
labels
Sep 21, 2021
alexec
added a commit
to alexec/argo-workflows
that referenced
this issue
Oct 20, 2021
…roj#6981 and argoproj#6732 Signed-off-by: Alex Collins <alex_collins@intuit.com>
alexec
added a commit
to alexec/argo-workflows
that referenced
this issue
Oct 20, 2021
…proj#6981 and argoproj#6732 Signed-off-by: Alex Collins <alex_collins@intuit.com>
alexec
added a commit
to alexec/argo-workflows
that referenced
this issue
Oct 20, 2021
…proj#6981 and argoproj#6732 Signed-off-by: Alex Collins <alex_collins@intuit.com>
alexec
changed the title
Agro event generate workflow name using epoch time cause duplicate name.
Argo event generate workflow name using epoch time cause duplicate name.
Oct 20, 2021
alexec
added a commit
that referenced
this issue
Oct 22, 2021
kriti-sc
pushed a commit
to kriti-sc/argo-workflows
that referenced
this issue
Oct 24, 2021
…roj#6981 and argoproj#6732 (argoproj#6995) Signed-off-by: Alex Collins <alex_collins@intuit.com> Signed-off-by: kriti-sc <kathuriakriti1@gmail.com>
alexec
added a commit
that referenced
this issue
Oct 24, 2021
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Create multiple workflow in same time via /api/v1/events/ cause problem.
Because argo try to generate name by itself using epoch time.
Testing :
create wf , wfbinding and request curl
Diagnostics
👀 Yes! We need all of your diagnostics, please make sure you add it all, otherwise we'll go around in circles asking you for it:
What Kubernetes provider are you using?
1.22
What version of Argo Workflows are you running?
3.1.0
What executor are you running? Docker/K8SAPI/Kubelet/PNS/Emissary
K8SAPI
Did this work in a previous version? I.e. is it a regression?
No
Are you pasting thousands of log lines? That's too much information.
The text was updated successfully, but these errors were encountered: