Skip to content

The kube-flannel pod on the edge node remains CrashLoopBackOff #575

@lengcangche-gituhub

Description

@lengcangche-gituhub

What happened:
The kube-flannel pod on the edge node remains CrashLoopBackOff.

What you expected to happen:
The kube-flannel pod on the edge node becomes Running.

How to reproduce it (as minimally and precisely as possible):
Install EdgeMesh as "https://edgemesh.netlify.app/guide/#dependencies"

Anything else we need to know?:
kubectl get nodes:
NAME STATUS ROLES AGE VERSION
ft-d2000-2-1 Ready none; 3h22m v1.28.14
gpu-nvidia-2 Ready agent,edge 179m v1.29.5-kubeedge-v1.19.0
npu-atlas-2 Ready control-plane 3h28m v1.28.14

where ft-d2000-2-1 and npu-atlas-2 are the nodes on the cloud, and CloudCore is deployed on ft-d2000-2-1.
gpu-nvidia-2 is the edge node.

When I use "kubectl describe" to describe the kube-flannel pod, the "install-cni-plugin" and "install-cni" container is Ready. The "kube-flanne" container's output is:
State: Terminated
Reason: Error
Exit Code: 1
Started: Sun, 24 Nov 2024 15:52:11 +0800
Finished: Sun, 24 Nov 2024 15:52:11 +0800
Last State: Terminated
Reason: Error
Exit Code: 1
Started: Sun, 24 Nov 2024 15:46:59 +0800
Finished: Sun, 24 Nov 2024 15:46:59 +0800
Ready: False

Restart Count: 27

Conditions:
Type Status
PodReadyToStartContainers True
Initialized True
Ready False
ContainersReady False
PodScheduled True

Events: none;

The kube-flannel pods that is deployed on another 2 nodes are Running.

kubectl get all -n kubeedge -o wide
NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
pod/cloudcore-587c8f99b5-lw8lq 1/1 Running 1 (4m55s ago) 62m 192.168.0.133 ft-d2000-2-1 <none> <none>
pod/edge-eclipse-mosquitto-p9gsz 1/1 Running 0 31m 192.168.42.62 gpu-nvidia-2 <none> <none>
pod/edgemesh-agent-64sj8 1/1 Running 0 2m27s 192.168.42.62 gpu-nvidia-2 <none> <none>
pod/edgemesh-agent-665nr 1/1 Running 0 2m27s 192.168.0.133 ft-d2000-2-1 <none> <none>
pod/edgemesh-agent-9d6j4 0/1 Terminating 0 31m 192.168.42.62 gpu-nvidia-2 <none> <none>
pod/edgemesh-agent-j9hwf 0/1 Terminating 0 40m 192.168.42.62 gpu-nvidia-2 <none> <none

Environment:

  • EdgeMesh version: image: kubeedge/edgemesh-agent:v1.17.0

  • Kubernetes version (use kubectl version):
    Client Version: v1.28.14
    Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
    Server Version: v1.28.14

  • KubeEdge version(e.g. cloudcore --version and edgecore --version): v1.19.0

  • Cloud nodes Environment:
    • Hardware configuration (e.g. lscpu):
      Architecture: aarch64
      CPU op-mode(s): 32-bit, 64-bit
      Byte Order: Little Endian
      CPU(s): 8
      On-line CPU(s) list: 0-7
      Thread(s) per core: 1
      Core(s) per socket: 8
      Socket(s): 1
      NUMA node(s): 1
      Vendor ID: 0x70
      Model: 3
      Model name: Phytium,D2000
      Stepping: 0x1
      CPU max MHz: 2000.0000
      CPU min MHz: 500.0000
      BogoMIPS: 3456.00
      L1d cache: 256 KiB
      L1i cache: 256 KiB
      L2 cache: 8 MiB
      L3 cache: 4 MiB
      NUMA node0 CPU(s): 0-7
      Flags: fp asimd evtstrm aes pmull sha1 sha2 crc32 cpuid
    • OS (e.g. cat /etc/os-release):
      NAME="Ubuntu"
      VERSION="20.04 LTS (Focal Fossa)"
      ID=ubuntu
      ID_LIKE=debian
      PRETTY_NAME="Ubuntu 20.04 LTS"
      VERSION_ID="20.04"
      HOME_URL="https://www.ubuntu.com/"
      SUPPORT_URL="https://help.ubuntu.com/"
      BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
      PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
      VERSION_CODENAME=focal
      UBUNTU_CODENAME=focal
    • Kernel (e.g. uname -a):
      Linux FT-D2000-2-1 4.19.15 Case "HTTPS GateWay": use "curl -k" is enough without key file #6 SMP Fri Sep 27 10:12:55 CST 2024 aarch64 aarch64 aarch64 GNU/Linux
    • Go version (e.g. go version): no
    • Others:
  • Edge nodes Environment:
    • edgecore version (e.g. edgecore --version):
      v1.19.0
      Additionally, I get the following output:
      E1124 17:42:55.306533 21163 server.go:119] listen tcp 127.0.0.1:10550: bind: address already in use
    • Hardware configuration (e.g. lscpu):
      Architecture: aarch64
      Byte Order: Little Endian
      CPU(s): 8
      On-line CPU(s) list: 0-7
      Thread(s) per core: 1
      Core(s) per socket: 2
      Socket(s): 4
      Vendor ID: Nvidia
      Model: 0
      Model name: ARMv8 Processor rev 0 (v8l)
      Stepping: 0x0
      CPU max MHz: 2035.2000
      CPU min MHz: 115.2000
      BogoMIPS: 62.50
      L1d cache: 64K
      L1i cache: 128K
      L2 cache: 2048K
      L3 cache: 4096K
      Flags: fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp
    • OS (e.g. cat /etc/os-release):
      NAME="Ubuntu"
      VERSION="18.04.6 LTS (Bionic Beaver)"
      ID=ubuntu
      ID_LIKE=debian
      PRETTY_NAME="Ubuntu 18.04.6 LTS"
      VERSION_ID="18.04"
      HOME_URL="https://www.ubuntu.com/"
      SUPPORT_URL="https://help.ubuntu.com/"
      BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
      PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
      VERSION_CODENAME=bionic
      UBUNTU_CODENAME=bionic
    • Kernel (e.g. uname -a):
      Linux GPU-Nvidia-2 4.9.253-tegra edgemesh code decoupling #1 SMP PREEMPT Mon Jul 26 12:19:28 PDT 2021 aarch64 aarch64 aarch64 GNU/Linux
    • Go version (e.g. go version): no
    • Others:

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/bugCategorizes issue or PR as related to a bug.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions