-
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
3.5 Pre-release: UI crashes when thare are archived workflows which has same name and namespace. #11371
Comments
The existing workflow with the same name+namespace should be deleted before submitting another one. Perhaps when performing resubmit, we should delete the existing one first? |
I think this issue does not relate to resubmitting itself. Before v3.4.8, the above situations work well because archived workflow is queried by following. get(uid: string, namespace: string) {
if (namespace === '') {
return requests.get(`api/v1/archived-workflows/${uid}`).then(res => res.body as models.Workflow);
} else {
return requests.get(`api/v1/archived-workflows/${uid}?namespace=${namespace}`).then(res => res.body as models.Workflow);
}
}, (Forgive me if I terribly taken something wrong) |
Support for get archived workflow by name+namespace is added in #11055. The assumption of using that is users would avoid submitting duplicate workflows. Perhap in the UI, we can stick with querying archived workflow by UID. Would you like to give that a try? |
@terrytangyuan and @toyamagu-2021 - given #11055 and UID querying, should we close this issue? |
This will be fixed in #11373 |
Pre-requisites
:latest
What happened/what you expected to happen?
Behaviour
To reproduce
Cause
argo-workflows/ui/src/app/shared/services/workflows-service.ts
Lines 69 to 70 in 22d4e17
argo-workflows/persist/sqldb/workflow_archive.go
Line 279 in 22d4e17
To resolve
argo-workflows/ui/src/app/workflows/components/workflows-container.tsx
Line 3 in 22d4e17
Version
master
Paste a small workflow that reproduces the issue. We must be able to run the workflow; don't enter a workflows that uses private images.
N/A
Logs from the workflow controller
Logs from in your workflow's wait container
The text was updated successfully, but these errors were encountered: