UI returns 500 on WorkflowTemplates tap if one WorkflowTemplate is invalid

[nice-pink]

Checklist

• [x] Double-checked my configuration.
• [x] Tested using the latest version.
• [x] Used the Emissary executor.

Summary

What happened/what you expected to happen?

I pushed a broken version of a WorkflowTempate to the cluster. Clicking on the WorkflowTemplates tap in the argo-workflows UI returns 500 and I can't see any WorkflowTemplates.

The error message is: "Unsuccessful HTTP response: json: cannot unmarshal object into Go struct field DAGTask.items.spec.templates.dag.tasks.template of type string"

I understand the behavior, it would still be nice to get a list of valid WorkflowTemplates.

What version are you running?

v3.3.8

Diagnostics

Paste the smallest workflow that reproduces the bug. We must be able to run the workflow.

apiVersion: argoproj.io/v1alpha1
kind: WorkflowTemplate
metadata:
  name: check-cond
spec:
  serviceAccountName: workflow
  templates:
    dag:
      tasks:
        - name: print
          template:
            name: go-print
            container:
              image: docker/whalesay:latest
              command: [cowsay]
              args: ["printed"]

---

Message from the maintainers:

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

[juliev0]

I was able to reproduce this and seems like a real bug. (Therefore, removing the "Triage" label.) I did also confirm that it works again if you delete the WorkflowTemplate.

[tooptoop4]

any fix? delete does not work either

[juliev0]

Unfortunately, there are higher priority items right now. Maybe somebody from the community can pick it up?

[alexec]

Work-around: delete the bad workflow template.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If this is a mentoring request, please provide an update here. Thank you for your contributions.

[stale[bot]]

This issue has been closed due to inactivity. Feel free to re-open if you still encounter this issue.