当前位置:   article > 正文

[kubernates]Unable to update cni config: No networks found in /etc/cni/net.d_unable to update cni config" err="no networks foun

unable to update cni config" err="no networks found in /etc/cni/net.d

kubernates join failed,response:

  1. Jun 10 11:22:57 00VMTL-FabricPeer-172-19-102-59 kubelet[19992]: W0610 11:22:57.514771 19992 cni.go:213] Unable to update cni config: No networks found in /etc/cni/net.d
  2. Jun 10 11:22:57 00VMTL-FabricPeer-172-19-102-59 kubelet[19992]: E0610 11:22:57.778191 19992 kubelet.go:2170] Container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:docker: network plugin is not ready: cni config uninitialized
  3. Jun 10 11:23:02 00VMTL-FabricPeer-172-19-102-59 kubelet[19992]: W0610 11:23:02.515736 19992 cni.go:213] Unable to update cni config: No networks found in /etc/cni/net.d
  4. Jun 10 11:23:02 00VMTL-FabricPeer-172-19-102-59 kubelet[19992]: E0610 11:23:02.780046 19992 kubelet.go:2170] Container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:docker: network plugin is not ready: cni config uninitialized
  5. Jun 10 11:23:07 00VMTL-FabricPeer-172-19-102-59 kubelet[19992]: W0610 11:23:07.516026 19992 cni.go:213] Unable to update cni config: No networks found in /etc/cni/net.d
  6. Jun 10 11:23:07 00VMTL-FabricPeer-172-19-102-59 kubelet[19992]: E0610 11:23:07.781684 19992 kubelet.go:2170] Container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:docker: network plugin is not ready: cni config uninitialized

 

analysising:

  1. kubectl get nodes
  2. NAME STATUS ROLES AGE VERSION
  3. 00vmdl-fabriccli-172-19-101-xx NotReady <none> 2m35s v1.14.3
  4. 00vmtl-fabricpeer-172-19-102-xx Ready <none> 7h42m v1.14.3
  5. 172-19-102-xx Ready <none> 24h v1.14.3
  6. 172-19-102-xx Ready master 25h v1.14.3

found one node NotReady

  1. kubectl get pods -n kube-system -o wide |grep 00vmdl-fabriccli-172-19-101-xx
  2. kube-flannel-ds-amd64-hk5sn 0/1 Init:0/1 0 8m49s 172.19.101.63 00vmdl-fabriccli-172-19-101-63 <none> <none>
  3. kube-proxy-vd7lp 1/1 Running 0 8m49s 172.19.101.63 00vmdl-fabriccli-172-19-101-63 <none> <none>

found the pod kube-flannel-ds-amd64-hk5sn has been init so long.we need analysis it further , look it's logs.

  1. kubectl --namespace kube-system logs kube-flannel-ds-amd64-hk5sn
  2. Error from server (BadRequest): container "kube-flannel" in pod "kube-flannel-ds-amd64-hk5sn" is waiting to start: PodInitializing

see the pod detail info:

  1. kubectl describe pod kube-flannel-ds-amd64-hk5sn --namespace=kube-system
  2. Events:
  3. Type Reason Age From Message
  4. ---- ------ ---- ---- -------
  5. Normal Scheduled 20m default-scheduler Successfully assigned kube-system/kube-flannel-ds-amd64-hk5sn to 00vmdl-fabriccli-172-19-101-63
  6. Warning Failed 17m kubelet, 00vmdl-fabriccli-172-19-101-63 Failed to pull image "quay.io/coreos/flannel:v0.11.0-amd64": rpc error: code = Unknown desc = net/http: TLS handshake timeout
  7. Warning Failed 17m kubelet, 00vmdl-fabriccli-172-19-101-63 Error: ErrImagePull
  8. Normal BackOff 17m kubelet, 00vmdl-fabriccli-172-19-101-63 Back-off pulling image "quay.io/coreos/flannel:v0.11.0-amd64"
  9. Warning Failed 17m kubelet, 00vmdl-fabriccli-172-19-101-63 Error: ImagePullBackOff
  10. Normal Pulling 17m (x2 over 20m) kubelet, 00vmdl-fabriccli-172-19-101-63 Pulling image "quay.io/coreos/flannel:v0.11.0-amd64"
  11. Warning Failed 10m kubelet, 00vmdl-fabriccli-172-19-101-63 Error: ErrImagePull
  12. Warning Failed 10m kubelet, 00vmdl-fabriccli-172-19-101-63 Failed to pull image "quay.io/coreos/flannel:v0.11.0-amd64": rpc error: code = Unknown desc = unexpected EOF
  13. Normal SandboxChanged 10m kubelet, 00vmdl-fabriccli-172-19-101-63 Pod sandbox changed, it will be killed and re-created.
  14. Normal BackOff 10m (x2 over 10m) kubelet, 00vmdl-fabriccli-172-19-101-63 Back-off pulling image "quay.io/coreos/flannel:v0.11.0-amd64"
  15. Warning Failed 10m (x2 over 10m) kubelet, 00vmdl-fabriccli-172-19-101-63 Error: ImagePullBackOff
  16. Normal Pulling 9m57s (x2 over 15m) kubelet, 00vmdl-fabriccli-172-19-101-63 Pulling image "quay.io/coreos/flannel:v0.11.0-amd64"
  17. Warning Failed 2m47s kubelet, 00vmdl-fabriccli-172-19-101-63 Failed to pull image "quay.io/coreos/flannel:v0.11.0-amd64": rpc error: code = Unknown desc = net/http: TLS handshake timeout
  18. Warning Failed 2m47s kubelet, 00vmdl-fabriccli-172-19-101-63 Error: ErrImagePull
  19. Normal BackOff 2m47s kubelet, 00vmdl-fabriccli-172-19-101-63 Back-off pulling image "quay.io/coreos/flannel:v0.11.0-amd64"
  20. Warning Failed 2m47s kubelet, 00vmdl-fabriccli-172-19-101-63 Error: ImagePullBackOff
  21. Normal Pulling 2m32s (x2 over 8m31s) kubelet, 00vmdl-fabriccli-172-19-101-63 Pulling image "quay.io/coreos/flannel:v0.11.0-amd64"
  22. Normal Pulling 33s kubelet, 00vmdl-fabriccli-172-19-101-63 Pulling image "quay.io/coreos/flannel:v0.11.0-amd64"

anyway,you need set the following param to comfirm close swap limit , otherways may cause error:

使用kubelet的启动参数–fail-swap-on=false去掉必须关闭Swap的限制。 修改/etc/sysconfig/kubelet,加入:

KUBELET_EXTRA_ARGS="--fail-swap-on=false"

 

声明:本文内容由网友自发贡献,不代表【wpsshop博客】立场,版权归原作者所有,本站不承担相应法律责任。如您发现有侵权的内容,请联系我们。转载请注明出处:https://www.wpsshop.cn/w/Cpp五条/article/detail/471077
推荐阅读
相关标签
  

闽ICP备14008679号