Comment 3 for bug 2052692

Thanks for the report. A few things may be going on here:

First, from you bundle, it looks like the machine constraints are quite low (2G mem, 16G disk). I know that's the default for k8s-core; we're addressing those in lp:2053058. I'm concerned that disk/oom issues may be manifesting as failing pods.

Second, there has been quite a bit of o7k integration refactoring in ck8s 1.29 (charms are out; docs are pending publish):

https://github.com/charmed-kubernetes/kubernetes-docs/blob/main/pages/k8s/openstack-integration.md

Third, i see you have the o7k-integrator co-located with kubernetes-control-plane. This isn't a typical supported env and i fear network stack conflicts.

Please let us know if this resolves itself with either:

1) larger machines
2) upgraded openstack integrator charms
3) modified topology to put the integrator on a separate machine

I'm going to set this bug to incomplete and targeting 1.29+ck1 for now. It would be great if you could attach a juju crashdump if you're still able to repro:

https://ubuntu.com/kubernetes/docs/troubleshooting#collecting-debug-information

Thanks!