-
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
v3.4.6+ Cannot access output global artifacts in exit handler after upgrade #11610
Comments
Based on initial triage. argo-workflows/workflow/controller/operator.go Line 3081 in f5e31f8
|
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as spam.
This comment was marked as spam.
An issue related to this one: the global output variables cannot be accessed in in exit handler either. Argo complains that |
Facing same issue as @Luobiny , are there any estimations to when this will be solved? |
canz #11738 🐝 📂 |
Pre-requisites
:latest
What happened/what you expected to happen?
Whenever we are calling the global output artifact in the exithandler Its failing with the error:
Bad Request: templates.exit-handler.steps failed to resolve
{{workflow.outputs.artifacts.output-result-car}}
This error was introduced after upgrading to the v3.4.6,. Also have tested with v3.4.7, v3.4.8, v3.4.9, v3.4.10 same issue persist.
After downgrading to v3.4.5 same workflow is working without any issue
Version
v3.4.6
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: