argo-workflows: Cannot read property type of undefined

Summary

What happened/what you expected to happen? I am trying to execute a workflow, and the ui return this error. I am expecting that i can see workflow ui correctly. http://localhost:2746/workflows/default/xxxxxx-pipeline-xxxx

Diagnostics

What version of Argo Workflows are you running? v2.11.0

Paste the workflow here, including status:
kubectl get wf -o yaml ${workflow}

Paste the logs from the workflow controller:
kubectl logs -n argo $(kubectl get pods -l app=workflow-controller -n argo -o name) | grep ${workflow}

Message from the maintainers:

Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.

About this issue

Original URL
State: closed
Created 4 years ago
Reactions: 7
Comments: 23 (17 by maintainers)

Commits related to this issue

fix(ui): Ignore referenced nodes that don't exist in UI. Fixes #4079 (#4099) — committed to argoproj/argo-workflows by simster7 4 years ago
fix(ui): Ignore referenced nodes that don't exist in UI. Fixes #4079 (#4099) — committed to argoproj/argo-workflows by simster7 4 years ago
fix(ui): Ignore referenced nodes that don't exist in UI. Fixes #4079 (#4099) Signed-off-by: Alex Capras <alexcapras@gmail.com> — committed to alexcapras/argo by simster7 4 years ago

Most upvoted comments

@saranyaeu2987 Thanks for attaching the workflow. Question: is this workflow the result of Retrying a previously failed workflow?

The issue is that the workflow is malformed (a node that is referenced by a parent node does not actually exist). This was intended to be fixed by #4028

I think that waitOnUpdate will still result in an error at it returns null.

The code calls setState before returning null, which is supposed to trigger a new React render. This is not happening for some reason, will investigate.

simster7 on Sep 22, 2020

Yes this is fixed

simster7 on Sep 21, 2020