-
Notifications
You must be signed in to change notification settings - Fork 1.1k
stats: skipped stopped containers on container list stats #3482
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
stats: skipped stopped containers on container list stats #3482
Conversation
|
cc @rphillips Does this make sense? we're seeing lots of |
|
@haircommander: GitHub didn't allow me to request PR reviews from the following users: rphillips. Note that only cri-o members and repo collaborators can review this PR, and authors cannot review their own PRs. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
1 similar comment
|
@haircommander: GitHub didn't allow me to request PR reviews from the following users: rphillips. Note that only cri-o members and repo collaborators can review this PR, and authors cannot review their own PRs. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Codecov Report
@@ Coverage Diff @@
## master #3482 +/- ##
==========================================
+ Coverage 40.47% 40.91% +0.43%
==========================================
Files 111 111
Lines 8943 8946 +3
==========================================
+ Hits 3620 3660 +40
+ Misses 4991 4950 -41
- Partials 332 336 +4 |
|
/retest provisioning :'( |
|
uhhhhh issue: containers/storage#575 edit: #3483 will make situations like this in the future fatal |
6990d00 to
56b1463
Compare
|
added some unit tests too, while I was here |
|
Would be nice to have a warning message that we're trying to get rid of in the first commit description, something like This helps to get rid of lots of warnings like this: Otherwise LGTM |
saschagrunert
left a comment
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.
LGTM
/retest
|
LGTM |
|
/test e2e-aws |
we have run into situations where cri-o reports a cgroup is deleted on list container stats calls, and it takes a while for cri-o to actually remove the container from the state. Stopped containers shouldn't matter with reporting stats, so we can skip them. This helps to get rid of lots of warnings like this: Unable to get stats for container XXX: unable to load cgroup at /kubepods.slice/kubepods-besteffort.slice/kubepods-besteffort-podXXX.slice: cgroup deleted Signed-off-by: Peter Hunt <[email protected]>
Signed-off-by: Peter Hunt <[email protected]>
7872407 to
4d21cd3
Compare
adopted as suggested 😄 |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: haircommander, mrunalp, saschagrunert The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/lgtm |
|
/retest |
1 similar comment
|
/retest |
What type of PR is this?
/kind bug
What this PR does / why we need it:
skip stopped containers when reporting stats
we have run into situations where cri-o reports a cgroup is deleted on list container stats calls, and it takes a while for cri-o to actually remove the container from the state. Stopped containers shouldn't matter with reporting stats, so we can skip them.
Which issue(s) this PR fixes:
should fix spammed logs here
also fixes #3259
Special notes for your reviewer:
Does this PR introduce a user-facing change?