-
Bug
-
Resolution: Done
-
Major
-
None
-
4.11.z
-
Quality / Stability / Reliability
-
False
-
-
None
-
Moderate
-
No
-
None
-
None
-
Proposed
-
CNF Network Sprint 238
-
1
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
All speaker pods stuck in crashloopbackoff. Re-creating metallb CR doesn't work:
$ oc get pods -l component=speaker -n metallb-system
NAME READY STATUS RESTARTS AGE
speaker-2ks47 5/6 CrashLoopBackOff 6 (111s ago) 7m56s
speaker-4bcc8 5/6 CrashLoopBackOff 6 (105s ago) 7m55s
speaker-68hk9 5/6 CrashLoopBackOff 6 (95s ago) 7m56s
speaker-6lqpb 5/6 CrashLoopBackOff 6 (2m5s ago) 7m56s
speaker-8pxzf 5/6 CrashLoopBackOff 6 (105s ago) 7m55s
speaker-mhkvm 5/6 CrashLoopBackOff 6 (109s ago) 7m56s
speaker-qzptv 5/6 CrashLoopBackOff 6 (110s ago) 7m56s
speaker-rjq9m 5/6 CrashLoopBackOff 6 (98s ago) 7m56s
speaker-v99zn 5/6 CrashLoopBackOff 6 (102s ago) 7m55s
speaker-vspfk 5/6 CrashLoopBackOff 6 (103s ago) 7m56s
speaker-zk259 5/6 CrashLoopBackOff 6 (100s ago) 7m55s
$ $ oc logs -c speaker speaker-68hk9 -n metallb-system
{"branch":"rhaos-4.11-rhel-8","caller":"main.go:94","commit":"2109a9ce65adeb1ee00fca6c78eb8a91988f4541","goversion":"gc / go1.18.10 / amd64","level":"info","msg":"MetalLB speaker starting (commit 2109a9ce65adeb1ee00fca6c78eb8a91988f4541, branch rhaos-4.11-rhel-8)","ts":"2023-06-20T10:57:40Z","version":""}
{"caller":"main.go:126","error":"open /etc/ml_secret_key/secretkey: no such file or directory","level":"error","msg":"failed to read memberlist secret key file","op":"startup","ts":"2023-06-20T10:57:40Z"}
Version-Release number of selected component (if applicable):
OCP 4.11.43
How reproducible:
Every time
Steps to Reproduce:
1. Install metallb operator and create metallb CR
Actual results:
All speaker pods crash and never start
Expected results:
Speaker pods to start all containers
Additional info:
This happened suddenly after restarting pods in 4.11.38 without any change done. Upgrading to 4.11.43 didn't do anything