search

kubernetes-retired / rktlet

[EOL] The rkt implementation of the Kubernetes Container Runtime Interface
Apache License 2.0
137 stars 43 forks source link

kubelet v1.10-beta.0 -> rktlet: http2Server.HandleStreams failed to read frame: read unix /var/run/rktlet.sock->@: read: connection reset by peer #183

Closed jforman closed 5 years ago

jforman commented 6 years ago

Kubelet v1.10-beta.0 rktlet: built from head (2018/02/22 @ 8am EST)

I tried running a yet-to-be-finalized k8s release as noted above to see if I could figure out why the kubelet was previously crashing (issue #182 ). Instead of crashing, I get these read errors. 


Feb 22 12:28:56 corea-worker0.obfuscated.domain.net kubelet[15768]: E0222 12:28:56.538250   15768 remote_runtime.go:69] Version from runtime service failed: rpc error: code = Unimplemented desc = unknown service runtime.v1alpha2.RuntimeService
Feb 22 12:28:56 corea-worker0.obfuscated.domain.net kubelet[15768]: E0222 12:28:56.538436   15768 kuberuntime_manager.go:172] Get runtime version failed: rpc error: code = Unimplemented desc = unknown service runtime.v1alpha2.RuntimeService
Feb 22 12:28:56 corea-worker0.obfuscated.domain.net kubelet[15768]: F0222 12:28:56.538530   15768 server.go:232] failed to run Kubelet: failed to create kubelet: rpc error: code = Unimplemented desc = unknown service runtime.v1alpha2.RuntimeService
Feb 22 12:28:56 corea-worker0.obfuscated.domain.net rktlet[15461]: 2018/02/22 12:28:56 transport: http2Server.HandleStreams failed to read frame: read unix /var/run/rktlet.sock->@: read: connection reset by peer
Feb 22 12:28:56 corea-worker0.obfuscated.domain.net systemd[1]: kubelet.service: Main process exited, code=exited, status=255/n/a
Feb 22 12:28:56 corea-worker0.obfuscated.domain.net systemd[1]: kubelet.service: Failed with result 'exit-code'.

2018/02/22 12:37:59 transport: http2Server.HandleStreams failed to read frame: read unix /var/run/rktlet.sock->@: read: connection reset by peer
qskousen commented 6 years ago

It appears rktlet does not support the newest CRI version of v1alpha2. https://kubernetes.io/docs/imported/release/notes/#major-themes

fejta-bot commented 5 years ago

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle stale

fejta-bot commented 5 years ago

Stale issues rot after 30d of inactivity. Mark the issue as fresh with /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle rotten

fejta-bot commented 5 years ago

Rotten issues close after 30d of inactivity. Reopen the issue with /reopen. Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /close

k8s-ci-robot commented 5 years ago

@fejta-bot: Closing this issue.

In response to [this](https://github.com/kubernetes-incubator/rktlet/issues/183#issuecomment-504655050): >Rotten issues close after 30d of inactivity. >Reopen the issue with `/reopen`. >Mark the issue as fresh with `/remove-lifecycle rotten`. > >Send feedback to sig-testing, kubernetes/test-infra and/or [fejta](https://github.com/fejta). >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.