-
Notifications
You must be signed in to change notification settings - Fork 3.6k
bugfix:close container io when runtime create failed #11885
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
Conversation
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 Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
bf0605a
to
8457b25
Compare
how it happened. @apostasie @AkihiroSuda
goroutine 5 [syscall]: new nerdctl ( pid 101727 )is hanging at flock to wait the lock to be release(old nerdctl 101602 hold the lock)
old nerdctl (pid 101602 )hang at goroutine 23 [select]:
old nerdctl (pid 101602 ) is waiting the shim to close the io , but shim forgot to close it when runtime create failed. |
can you review this pr? thank you @fuweid @samuelkarp @mikebrow |
8457b25
to
353831b
Compare
6ba97f6
to
56b10ce
Compare
Signed-off-by: ningmingxiao <ning.mingxiao@zte.com.cn>
56b10ce
to
e6708bd
Compare
ping @fuweid @AkihiroSuda |
/ok-to-test |
/cherry-pick release/2.1 |
@AkihiroSuda: new pull request created: #12009 In 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-sigs/prow repository. |
/cherry-pick release/2.0 |
@austinvazquez: new pull request created: #12051 In 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-sigs/prow repository. |
fix:#11890
ping @AkihiroSuda @samuelkarp @mikebrow @mxpv