Uploading the CRI Socket information ends up with error uploading crisocket!

Question

Uploading the CRI Socket information ends up with error uploading crisocket!

PontusTideman opened this issue 4 years ago · comments

So, first things first!

For the last couple of weeks we have tried to pin point what is going on and what is not working. Everytime we ends up with both patchnode.go:30] [patchnode] Uploading the CRI Socket information "/var/run/dockershim.sock" to the Node API object "DELTED_INFO" as an annotation [kubelet-check] Initial timeout of 40s passed. timed out waiting for the condition error uploading crisocket

The setup is running on Debain 10, with Docker and Kubernetes + Flannel as the CNI. All ports that is necessary for it to work is open, and we even allowed all traffic between the cluster, but everytime we ends up with the crisocket time out as above.

Today I did a reset on master + slaves, replaced the Flannel CNI with Calico and all went well!

The only thing I did was to replace the Flannel with Calico, everything else is untouched. So it looks like there is a problem with the CRI plugin and the Flannel CNI, but I can't put a finger on it what is not working.

Sergey Kanzhelev commented 4 years ago

/close

fejta-bot · Answer 1 · Mon Sep 14 2020 23:46:00 GMT+0800 (China Standard Time)

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

Pontus Tideman · Answer 2 · Tue Sep 15 2020 12:06:50 GMT+0800 (China Standard Time)

/remove-lifecycle stale

fejta-bot · Answer 3 · Mon Dec 14 2020 13:06:44 GMT+0800 (China Standard Time)

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

Pontus Tideman · Answer 4 · Tue Dec 15 2020 20:08:49 GMT+0800 (China Standard Time)

/remove-lifecycle stale

Sergey Kanzhelev · Answer 5 · Wed Mar 03 2021 14:10:54 GMT+0800 (China Standard Time)

@PontusTideman you may have more luck filing this issue in kubernetes repository. This repository is managed by bot as a copy of a folder in kubernetes repository.

Kubernetes Prow Robot · Answer 6 · Wed Mar 03 2021 14:12:06 GMT+0800 (China Standard Time)

@SergeyKanzhelev: Closing this issue.

In response to this:

/close

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.