-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
"internal server error" on the UI when viewing the logs ("no template found" error) #9644
Closed
2 of 3 tasks
Labels
Comments
3 tasks
I think this also relates to #9631 |
Closed
3 tasks
@brianloss are you able to assign yourself this? It looks like I can't assign it to you. (if you add a comment here I believe I can, though) Thank you for looking into it! |
@juliev0 No, I don't have permissions to assign, but let's see if this comment helps. |
terrytangyuan
pushed a commit
that referenced
this issue
Sep 21, 2022
…9644. (#9648) * fix: Fixed artifact retrieval when templateRef in use. Fixes #9631. Signed-off-by: Brian Loss <[email protected]> * chore: Address review feedback - use util method * Expose getTemplateFromNode in workflow/util/util.go * Update uses of getTemplateFromNode to GetTemplateFromNode * Call GetTemplateFromNode in artifact_server.go Signed-off-by: Brian Loss <[email protected]> Signed-off-by: Brian Loss <[email protected]>
juchaosong
pushed a commit
to juchaosong/argo-workflows
that referenced
this issue
Nov 3, 2022
…#9631, argoproj#9644. (argoproj#9648) * fix: Fixed artifact retrieval when templateRef in use. Fixes argoproj#9631. Signed-off-by: Brian Loss <[email protected]> * chore: Address review feedback - use util method * Expose getTemplateFromNode in workflow/util/util.go * Update uses of getTemplateFromNode to GetTemplateFromNode * Call GetTemplateFromNode in artifact_server.go Signed-off-by: Brian Loss <[email protected]> Signed-off-by: Brian Loss <[email protected]> Signed-off-by: juchao <[email protected]>
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Pre-requisites
:latest
What happened/what you expected to happen?
Upgraded to version 3.4.0 with the new helm chart version 0.18.0.
After upgrading we see the logs of a step of the main container while it is currently running. As soon as that step is finished we are getting "internal server error" on the UI when viewing the logs for the main container (we can see the logs for the init and the wait container).
This only happens when you call a cluster workflow which in turn calls another cluster workflow (see my example).
For example, if you call the cluster workflow cwt-2 directly without cwt-1, you can see the logs in the UI.
It works even if the workflow fails. For example, if you remove "serviceAccountName: argo-wf-sa", the workflow is marked as failed (
Error (exit code 1): pods ... is forbidden: User "...:default" cannot patch resource "pods" in API group "" in the namespace ...
), but you can then see the logs in the UI.Log output from the workflow server pod:
Version
3.4.0
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.
Logs from the workflow controller
Logs from in your workflow's wait container
The text was updated successfully, but these errors were encountered: