Skip to content
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

fix error log of crio client #3144

Merged
merged 1 commit into from
Aug 2, 2022

Conversation

yangjunmyfm192085
Copy link
Contributor

In the kubernetes main branch, the following exception log appears in the kubelet log

E0729 01:14:33.037428  170935 manager.go:1123] Failed to create existing container: /system.slice/crio-ccc008b39f6ce2e2bfa0bbda7d8873d0164a7917a4c469ad2fbb5fc50ecb98b1.scope: Error finding container ccc008b39f6ce2e2bfa0bbda7d8873d0164a7917a4c469ad2fbb5fc50ecb98b1: Status 404 returned error &{%!s(*http.body=&{0xc0025f5bd8 <nil> <nil> false false {0 0} false false false <nil>}) {%!s(int32=0) %!s(uint32=0)} %!s(bool=false) <nil> %!s(func(error) error=0x835360) %!s(func() error=0x835460)}

The following log information output is wrong
return nil, fmt.Errorf("Error finding container %s: Status %d returned error %s", id, resp.StatusCode, resp.Body)

After the update, the log information is as follows

E0729 02:59:50.722242  317325 manager.go:1123] Failed to create existing container: /system.slice/crio-eef4eeae4c31f001314dc155cb20012ddf3ff25400e0bfb097ccacac98006935.scope: Error finding container eef4eeae4c31f001314dc155cb20012ddf3ff25400e0bfb097ccacac98006935: Status 404 returned error can't find the container with id eef4eeae4c31f001314dc155cb20012ddf3ff25400e0bfb097ccacac98006935

@google-cla
Copy link

google-cla bot commented Jul 29, 2022

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

@k8s-ci-robot
Copy link
Collaborator

Hi @yangjunmyfm192085. Thanks for your PR.

I'm waiting for a google 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.

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/test-infra repository.

@yangjunmyfm192085
Copy link
Contributor Author

/retest

@k8s-ci-robot
Copy link
Collaborator

@yangjunmyfm192085: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/retest

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/test-infra repository.

@yangjunmyfm192085
Copy link
Contributor Author

/ok-to-test

@yangjunmyfm192085
Copy link
Contributor Author

/cc @bobbypage

@bobbypage
Copy link
Collaborator

/ok-to-test

@bobbypage
Copy link
Collaborator

LGTM

@bobbypage bobbypage merged commit 86b11c6 into google:master Aug 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants