Skip to content

cri:use debug level when receive exec process exited events#11838

Merged
mxpv merged 1 commit intocontainerd:mainfrom
ningmingxiao:debug_exec_event
May 13, 2025
Merged

cri:use debug level when receive exec process exited events#11838
mxpv merged 1 commit intocontainerd:mainfrom
ningmingxiao:debug_exec_event

Conversation

@ningmingxiao
Copy link
Copy Markdown
Contributor

@ningmingxiao ningmingxiao commented May 12, 2025

if use exec to do some health check will generate many exec exited events log.
fix:#11836
@AkihiroSuda @mxpv can you review this pr ? It is easily to review. Thanks.

@k8s-ci-robot
Copy link
Copy Markdown

Hi @ningmingxiao. 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 the area/cri Container Runtime Interface (CRI) label May 12, 2025
@github-project-automation github-project-automation Bot moved this from Needs Triage to Review In Progress in Pull Request Review May 13, 2025
@mxpv mxpv added this pull request to the merge queue May 13, 2025
Merged via the queue into containerd:main with commit 58cd333 May 13, 2025
56 checks passed
@github-project-automation github-project-automation Bot moved this from Review In Progress to Done in Pull Request Review May 13, 2025
@ningmingxiao ningmingxiao deleted the debug_exec_event branch May 13, 2025 04:25
@AkihiroSuda
Copy link
Copy Markdown
Member

/cherry-pick release/2.1

@k8s-infra-cherrypick-robot
Copy link
Copy Markdown

@AkihiroSuda: new pull request created: #11848

Details

In response to this:

/cherry-pick release/2.1

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.

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) cherry-picked/2.1.x PR commits are cherry picked into the release/2.1 branch needs-ok-to-test size/XS

Projects

Archived in project

Development

Successfully merging this pull request may close these issues.

6 participants