kata-containers/runtime

Failed to check if grpc server is working: rpc error: code = Unavailable desc = transport is closing: unknown

free2k opened this issue · 6 comments

free2k commented

Get your issue reviewed faster

The information provided will help us to understand the problem more quickly
so saves time for both of us! 😄

Description of problem

Error when creating kata container

Expected result

The kata container was created successfully

Actual result

Nov 04 21:44:58 myhost containerd[200081]: time="2020-11-04T21:44:58.637898529+08:00" level=warning msg="sandox cgroups path is empty" ID=5d9f54d34584b5d2cd439e4bd481615796d4baae5172947e5400e2c8bf881386 sandbox=5d9f54d34584b5d2cd439e4bd481615796d4baae5172947e5400e2c8bf881386 source=virtcontainers subsystem=sandbox
Nov 04 21:44:58 myhost containerd[200081]: time="2020-11-04T21:44:58.640798015+08:00" level=info msg="shim disconnected" id=5d9f54d34584b5d2cd439e4bd481615796d4baae5172947e5400e2c8bf881386
Nov 04 21:44:59 myhost containerd[200081]: time="2020-11-04T21:44:59.250108344+08:00" level=error msg="RunPodSandbox for &PodSandboxMetadata{Name:trade-emergency-test-920d80a34205d924fb8deb35208aea78-y7g7b,Uid:c91278c4-1ea3-11eb-bd94-0a580a308f97,Namespace:test,Attempt:0,} failed, error" error="failed to create containerd task: Failed to check if grpc server is working: rpc error: code = Unavailable desc = transport is closing: unknown"
Nov 04 21:45:12 myhost containerd[200081]: time="2020-11-04T21:45:12.508998670+08:00" level=info msg="RunPodsandbox for &PodSandboxMetadata{Name:trade-emergency-test-920d80a34205d924fb8deb35208aea78-y7g7b,Uid:c91278c4-1ea3-11eb-bd94-0a580a308f97,Namespace:test,Attempt:0,}"

Further information

Version used
kata-runtime-1.10.1
kata-proxy-1.10.1

free2k commented

It should be that the kata-agent failed to start, the key problem occasionally appeared, and it cannot be reproduced now

jodh-intel commented

Thanks for raising @free2k, but you haven't provided the information requested in the template which we really need to see 😄

Also, can you try to recreate using 1.10.8 with full debug enabled? (or indeed with 1.11.5, 1.12.0-rc0 or 2.0.0).

free2k commented

Thanks for raising @free2k, but you haven't provided the information requested in the template which we really need to see 😄

Also, can you try to recreate using 1.10.8 with full debug enabled? (or indeed with 1.11.5, 1.12.0-rc0 or 2.0.0).

I have opened debug now, but it cannot be reproduced now. There is only a very small chance

jodh-intel commented

@free2k - I suggest you update the version of Kata you are using to one of those I mentioned above. If you can recreate the problem then, please provide further details. Otherwise, there isn't much we can do I'm afraid.

fidencio commented

This issue is being automatically closed as Kata Containers 1.x has now reached EOL (End of Life). This means it is no longer being maintained.

Important:

All users should switch to the latest Kata Containers 2.x release to ensure they are using a maintained release that contains the latest security fixes, performance improvements and new features.

This decision was discussed by the @kata-containers/architecture-committee and has been announced via the Kata Containers mailing list:

If you believe this issue still applies to Kata Containers 2.x, please open an issue against the Kata Containers 2.x repository, pointing to this one, providing details to allow us to migrate it.