kube-ovn stuck: Waiting to retry configuring Kube-OVN
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Kube OVN Charm |
Invalid
|
Medium
|
Unassigned | ||
Kubernetes Control Plane Charm |
Fix Released
|
Medium
|
George Kraft | ||
Kubernetes Worker Charm |
Fix Released
|
Medium
|
George Kraft |
Bug Description
In testrun https:/
```
kubernetes-
canonical-
containerd/7 active idle 10.244.8.137 Container runtime available
kube-ovn/7 active idle 10.244.8.137
ntp/10 active idle 10.244.8.137 123/udp chrony: Ready
kubernetes-
canonical-
containerd/8 active idle 10.244.8.139 Container runtime available
kube-ovn/8 waiting idle 10.244.8.139 Waiting to retry configuring Kube-OVN
ntp/11 active idle 10.244.8.139 123/udp chrony: Ready
```
In the logs we see:
```
2023-02-13 10:02:08 ERROR unit.kube-
File "./src/charm.py", line 342, in configure_kube_ovn
self.
File "./src/charm.py", line 655, in wait_for_
self.
File "./src/charm.py", line 666, in wait_for_rollout
self.kubectl(
File "./src/charm.py", line 464, in kubectl
return check_output(cmd)
File "/usr/lib/
return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
File "/usr/lib/
raise CalledProcessEr
subprocess.
```
This doesn't tell us much about what actually is going wrong, unfortunately.
Crashdumps and configs are found here:
https:/
Changed in charm-kubernetes-master: | |
status: | Fix Committed → Fix Released |
Changed in charm-kubernetes-worker: | |
status: | Fix Committed → Fix Released |
Changed in charm-kube-ovn: | |
status: | Triaged → Invalid |
This is not limited to focal, we see it on jammy too: https:/ /oil-jenkins. canonical. com/artifacts/ d6cf7339- e435-4660- 860b-0d37b401a7 d9/index. html