Fix/nil pointer reference in updateBuildRunUsingTaskRunCondition #592
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes
There seems to be a rather rare case where we have a setup in which a TaskRun
has a completion timestamp and condition reason
TaskRunReasonFailed
, whilethe respective pod has containers which are not terminated, (yet). In this
case the code ends up with a nil pointer dereferences and crashes the running
operator pod. See #591 for details.
Fixes #591
Submitter Checklist
See the contributor guide
for details on coding conventions, github and prow interactions, and the code review process.
Release Notes