Skip to content

[release/2.0] cri: fix lost container exit events if they arrive before info is cached#11657

Closed
k8s-infra-cherrypick-robot wants to merge 1 commit intocontainerd:release/2.0from
k8s-infra-cherrypick-robot:cherry-pick-11579-to-release/2.0
Closed

[release/2.0] cri: fix lost container exit events if they arrive before info is cached#11657
k8s-infra-cherrypick-robot wants to merge 1 commit intocontainerd:release/2.0from
k8s-infra-cherrypick-robot:cherry-pick-11579-to-release/2.0

Conversation

@k8s-infra-cherrypick-robot

This is an automated cherry-pick of #11579

/assign samuelkarp

@k8s-ci-robot
Copy link

Hi @k8s-infra-cherrypick-robot. Thanks for your PR.

I'm waiting for a containerd member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

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-sigs/prow repository.

@dosubot dosubot bot added area/cri Container Runtime Interface (CRI) kind/bug labels Apr 7, 2025
@samuelkarp
Copy link
Member

Closing per #11579 (comment)

@samuelkarp samuelkarp closed this Apr 7, 2025
@github-project-automation github-project-automation bot moved this from Needs Triage to Done in Pull Request Review Apr 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/cri Container Runtime Interface (CRI) kind/bug needs-ok-to-test size/S

Projects

Archived in project

Development

Successfully merging this pull request may close these issues.

4 participants