-
Notifications
You must be signed in to change notification settings - Fork 3.8k
Remove entry for container from container store on error #8414
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 @kiashok. 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. DetailsInstructions 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. |
3139aaa to
b17a05a
Compare
b17a05a to
591bbd1
Compare
|
close #8425 |
591bbd1 to
2dd47ac
Compare
If containerd does not see a container but criservice's container store does, then we should try to recover from this error state by removing the container from criservice's container store as well. Signed-off-by: Kirtana Ashok <[email protected]>
2dd47ac to
d9f3e38
Compare
|
@fuweid addressed your review comment. Could you please take a look? Thanks! |
fuweid
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
If containerd does not see a container but criservice's container store does, then we should try to recover from this error state by removing the container from criservice's container store as well.