kube_ovn deployments on arm get stuck waiting for 2 kube_ovn pods to start

Bug #1999443 reported by Alexander Balderson
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Kube OVN Charm
New
Undecided
Unassigned

Bug Description

When deploying k8s 1.26 on baremetal arm, k8s-cp gets stuck waiting for 2 pods to start. The logs are showing that the pods its waiting for are kube-ovn-pinger.

I cant tell what is causing the pods to fail to start from the logs, but SQA can try to spin up a live environment reproducing the issue if needed.

the testrun can be found at:
https://solutions.qa.canonical.com/v2/testruns/a8fa0aad-be4e-4c47-88b0-954880daa3b9/

and crashdump at:
https://oil-jenkins.canonical.com/artifacts/a8fa0aad-be4e-4c47-88b0-954880daa3b9/generated/generated/kubernetes-maas/juju-crashdump-kubernetes-maas-2022-12-10-01.28.25.tar.gz

with bundle at:
https://oil-jenkins.canonical.com/artifacts/a8fa0aad-be4e-4c47-88b0-954880daa3b9/generated/generated/kubernetes-maas/bundle.yaml

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.