ilkilab/agorakube

Metallb speakers pods failed with "CrashLoopBackOff" Status

Closed this issue · 2 comments

mathieubodin commented

Describe the bug
As stated in the title, metallb speakers pods failed with "CrashLoopBackOff" Status.

To Reproduce
Steps to reproduce the behavior:

  1. Install a cluster with Metallb enabled

Expected behavior
Metallb is installed and work properly

Screenshots
Got the following events on a given pod:

Events:
  Type     Reason   Age                     From                                 Message
  ----     ------   ----                    ----                                 -------
  Warning  BackOff  12m (x416 over 102m)    kubelet, worker7  Back-off restarting failed container
  Normal   Pulled   8m25s                   kubelet, worker7l  Successfully pulled image "metallb/speaker:v0.9.3" in 931.035286ms
  Normal   Pulled   8m8s                    kubelet, worker7  Successfully pulled image "metallb/speaker:v0.9.3" in 1.041470424s
  Normal   Pulled   7m40s                   kubelet, worker7  Successfully pulled image "metallb/speaker:v0.9.3" in 1.448880813s
  Normal   Pulling  6m53s (x4 over 8m26s)   kubelet, worker7  Pulling image "metallb/speaker:v0.9.3"
  Normal   Created  6m52s (x4 over 8m25s)   kubelet, worker7  Created container speaker
  Warning  Failed   6m52s (x4 over 8m25s)   kubelet, worker7  Error: failed to create containerd task: OCI runtime create failed: container_linux.go:349: starting container process caused "process_linux.go:449: container init caused \"setenv: invalid argument\"": unknown
  Normal   Pulled   6m52s                   kubelet, worker7  Successfully pulled image "metallb/speaker:v0.9.3" in 1.437355748s
  Warning  BackOff  3m11s (x25 over 8m24s)  kubelet, worker7  Back-off restarting failed container

Additional context
Observed on Kernetes v1.19.3 installed with agorakube branch core

github-actions commented

Stale issue message

github-actions commented

Automatically closed due to no activity