-
Notifications
You must be signed in to change notification settings - Fork 1.1k
crio:fix a bug about log container #5843
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
Signed-off-by: jiang wei <[email protected]>
|
Hi @jwcesign. Thanks for your PR. I'm waiting for a cri-o 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. |
|
/assign @haircommander |
|
yeah this makes sense /ok-to-test thanks @jwcesign |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: haircommander, jwcesign 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 |
|
I check the integration test case, the looks like unpause container work not on time sometimes, it cause failed case when finish. |
|
/retest |
|
yeah that make sense to me! we're going to cut 1.24.0 today, so it'll have to be backported /lgtm |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest |
crio:fix a bug about log container
crio:fix a bug about log container
Signed-off-by: jiang wei [email protected]
What type of PR is this?
/kind bug
What this PR does / why we need it:
When container is in unknown state, will have this error when log it(using critl and kubectl).

fix bug to log container, in upper layer interface, we need
status.CreatedAtWhich issue(s) this PR fixes:
none