openstack-cloud-controller-manager pods can't connect to k8s api after upgrade after upgrade
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Openstack Integrator Charm |
New
|
Undecided
|
Unassigned |
Bug Description
After an upgrade of the openstack integrator charm to
1.28/stable 69 on a cloud using k8s 1.24 (upgraded from 1.23)
we see errors from most of the the openstack-
```
E0424 00:09:16.841262 1 leaderelection.
```
and
```
E0424 13:45:42.209919 1 leaderelection.
```
and
```
E0424 13:53:02.277675 1 controller.go:310] error processing service kong/kong-
```
These pods required a manual delete to get them back healthily talking to the k8s api.