-
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
{{ workflow.failures }}
doesn't get a value in lifecycle hook
#8882
Comments
Looking at the doco, it's made clear that the |
@ezk84 facing the similar issue! 😅 Glad you opened an issue! I was about to! {{workflow.failures}} was not holding any data. Also there are few issues which I observed using lifecycle hooks and HTTP templates.
|
It is a bug argo-workflows/workflow/controller/operator.go Lines 389 to 409 in 093a6fe
This block of code needs to move above
you can convert the block of code as function and call. Do you like to submit the PR for this? |
@ezk84 are you planing to submit the PR for this issue? |
@sarabala1979 I will attempt it. Tried to get a dev environment running, though I run into problems with the vscode devcontainer. I imagine I would have to write at least a test to validate this, no? |
need test. Let me know if you have any problem setting up local env |
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. |
Signed-off-by: Ezequiel Muns <[email protected]>
Signed-off-by: Ezequiel Muns <[email protected]>
Signed-off-by: Ezequiel Muns <[email protected]>
🕺 Great! |
…oproj#9009) Signed-off-by: Ezequiel Muns <[email protected]> Signed-off-by: Loric ANDRE <[email protected]>
…oproj#9009) Signed-off-by: Ezequiel Muns <[email protected]> Signed-off-by: Reddy <[email protected]>
{{ workflow.failures }}
doesn't get a value in lifecycle hook
Checklist
Summary
What happened/what you expected to happen?
The message that is output by the hook named
on-fail
should have the{{ workflow.failures }}
replaced by a JSON object as per the documentation.Instead the literal string
{{ workflow.failures }}
gets output.This is also visible when one inspects the INPUTS/OUTPUTS tab in the Workflow Details view in the UI.
What version are you running?
Diagnostics
Paste the smallest workflow that reproduces the bug. We must be able to run the workflow.
Logs from the workflow controller:
The workflow's pods that are problematic:
Pods:
Logs from in your workflow's wait container:
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: