-
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
Exit handler nil pointer crash when failed step misses output parameter #13445
Labels
area/exit-handler
area/hooks
P2
Important. All bugs with >=3 thumbs up that aren’t P0 or P1, plus: Any other bugs deemed important
type/bug
Milestone
Comments
bmjhversteeg
changed the title
Exit handler crashes when failed step has misses output parameter
Exit handler crashes when failed step misses output parameter
Aug 9, 2024
agilgur5
changed the title
Exit handler crashes when failed step misses output parameter
Exit handler crash due to nil pointer when failed step misses output parameter
Aug 9, 2024
For other readers, there's a stack trace within the logs:
I'll reformat that if I get a chance. EDIT: reformatted below:
|
agilgur5
changed the title
Exit handler crash due to nil pointer when failed step misses output parameter
Exit handler nil pointer crash when failed step misses output parameter
Aug 9, 2024
agilgur5
added
P2
Important. All bugs with >=3 thumbs up that aren’t P0 or P1, plus: Any other bugs deemed important
and removed
P3
Low priority
labels
Aug 10, 2024
Joibel
pushed a commit
to pipekit/argo-workflows
that referenced
this issue
Sep 19, 2024
…roj#13445 (argoproj#13448) Signed-off-by: Miltiadis Alexis <alexmiltiadis@gmail.com>
Joibel
pushed a commit
that referenced
this issue
Sep 20, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area/exit-handler
area/hooks
P2
Important. All bugs with >=3 thumbs up that aren’t P0 or P1, plus: Any other bugs deemed important
type/bug
Pre-requisites
:latest
image tag (i.e.quay.io/argoproj/workflow-controller:latest
) and can confirm the issue still exists on:latest
. If not, I have explained why, in detail, in my description below.What happened? What did you expect to happen?
When an exit handler is called on a failed step that has an output parameter which is null/empty (because the step crashed before creating the output file used in
valueFrom
), the exit handler fails with the message:runtime error: invalid memory address or nil pointer dereference
. Seems similar to #12288 but in this case, the output params assumed to be always present.Originally tested on v3.5.5 but also present in 3.5.10
Version(s)
v3.5.5, v3.5.10
Paste a minimal 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: