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
UI crash when viewing YAML of nodes in workflows using workflowTemplateRef
#4691
Comments
Can I please ask for your complete workflow YAML? |
I've created a dev build for you to test: |
Ok. Please attach the YAML of your workflow so I don't go round in circles on this please. Thank you. |
Sure. For me this is happens with basically all workflows. So for example this template
Resulting in this workflow
|
It also happens for me for non-archived workflows. |
I've created a new dev build for you to test: |
Thx. I'll test. Just to make sure, the image tag is supposed to be the same as the previous test build? |
So I think it is the wrong solution. |
@paalkr how's your React? |
Sorry, I'm not a developer, but a Cloud Native infra architect and ops person. |
workflowTemplateRef
@paalkr does the problem resolve when you refresh the page? |
Unfortunately refreshing the page does not make any difference. |
…argoproj#4691 Signed-off-by: Alex Collins <alex_collins@intuit.com>
@alexec , does it exist a test / master image with this fix included? I appreciate that your support on this issue, thx! |
I noticed that the same test-build was updated to include the latest commit. To me it looks like the problem is solved! |
Summary
View the yaml def of archived workflows does not work in 2.12-rc4, and will render a stack trace error in the UI
Images from 2.12-rc4 (BTW, the same problem occurs if click on the Containers tab)
The same use case does work in 2.11.8
Diagnostics
Kops k8s 1.17.13 on AWS
2.12-rc4
There are no errors in the server logs and the workflow controller logs.
Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.
The text was updated successfully, but these errors were encountered: