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.
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
fix(pkg/repository/maintenance): handle when there's no container status #8271
base: main
Are you sure you want to change the base?
fix(pkg/repository/maintenance): handle when there's no container status #8271
Changes from all commits
1e3e027
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
Check warning on line 124 in pkg/repository/maintenance.go
Codecov / codecov/patch
pkg/repository/maintenance.go#L124
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The termination-log is not always written, it is only written when maintenance fails.
So I suspect it is a non-error case when
len(statuses) == 0
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
to me, "no statuses" is not the expected state even if the container terminated successfully:
https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#container-state-terminated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry I may have pointed the comment to wrong code. The most suspecting line is below:
As you can see from the maintenance code, if the maintenance succeeds, no termination message is written, so
statuses[0].State.Terminated
may indeed be nil. But this is a normal case.Furthermore, when nothing is set to
pod.Status.ContainerStatuses
, will it be nil? If so, it is still a normal case.Please double confirm this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I answered to the
State.Terminated
case too :) there's not just the termination log, there's also the exit code, time, etc.About container statuses, they are expected to be filled (from waiting to running to terminated) but they may not be present when the pod was just created (I guess a kind of race condition leads the initial but mentioned here). So, my interpretation is that when it's empty, it's not a normal state and can't be after the container's termination: ie, the caller made the call too soon for some reason, very in line with semantics of asking before the pod was created by the job, which is a case that returns an error.
Check warning on line 130 in pkg/repository/maintenance.go
Codecov / codecov/patch
pkg/repository/maintenance.go#L130