Name: capo-controller-manager-56cf844ccd-v9h2w Namespace: capo-system Priority: 0 Service Account: capo-manager Node: instance/199.19.213.241 Start Time: Tue, 30 Jun 2026 18:50:14 +0000 Labels: cluster.x-k8s.io/provider=infrastructure-openstack control-plane=capo-controller-manager pod-template-hash=56cf844ccd Annotations: Status: Running SeccompProfile: RuntimeDefault IP: 10.0.0.14 IPs: IP: 10.0.0.14 Controlled By: ReplicaSet/capo-controller-manager-56cf844ccd Containers: manager: Container ID: containerd://38263ef3e1d4987a0dd74d211f57509111982600d3c83b219b2fe13033927379 Image: harbor.atmosphere.dev/registry.k8s.io/capi-openstack/capi-openstack-controller:v0.14.4 Image ID: harbor.atmosphere.dev/registry.k8s.io/capi-openstack/capi-openstack-controller@sha256:b428de23d97c69ebb350e2359e73eb6ec92572e5dfab8cc4cea9994c01fa4ee0 Ports: 9443/TCP, 9440/TCP Host Ports: 0/TCP, 0/TCP Command: /manager Args: --leader-elect --v=2 --diagnostics-address=127.0.0.1:8080 --insecure-diagnostics=true --feature-gates=PriorityQueue=false,AutoScaleFromZero=false State: Running Started: Tue, 30 Jun 2026 18:55:48 +0000 Last State: Terminated Reason: Error Message: tackfloatingippool" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackFloatingIPPool" worker count=1 I0630 18:54:19.604976 1 controller.go:286] "Starting Controller" controller="openstackcluster" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackCluster" I0630 18:54:19.605000 1 controller.go:289] "Starting workers" controller="openstackcluster" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackCluster" worker count=10 I0630 18:54:19.605018 1 controller.go:286] "Starting Controller" controller="openstackmachine" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackMachine" I0630 18:54:19.605050 1 controller.go:286] "Starting Controller" controller="openstackserver" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackServer" I0630 18:54:19.605055 1 controller.go:289] "Starting workers" controller="openstackmachine" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackMachine" worker count=10 I0630 18:54:19.605058 1 controller.go:289] "Starting workers" controller="openstackserver" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackServer" worker count=10 E0630 18:54:35.926754 1 leaderelection.go:441] Failed to update lock optimistically: the server was unable to return a response in the time allotted, but may still be processing the request (put leases.coordination.k8s.io controller-leader-election-capo), falling back to slow path E0630 18:54:40.926586 1 leaderelection.go:484] Failed to update lock: Put "https://10.96.0.1:443/apis/coordination.k8s.io/v1/namespaces/capo-system/leases/controller-leader-election-capo?timeout=5s": context deadline exceeded I0630 18:54:40.926643 1 leaderelection.go:297] failed to renew lease capo-system/controller-leader-election-capo: context deadline exceeded E0630 18:54:45.875835 1 main.go:304] "problem running manager" err="leader election lost" logger="setup" Exit Code: 1 Started: Tue, 30 Jun 2026 18:54:02 +0000 Finished: Tue, 30 Jun 2026 18:54:45 +0000 Ready: True Restart Count: 2 Liveness: http-get http://:healthz/healthz delay=0s timeout=1s period=10s #success=1 #failure=3 Readiness: http-get http://:healthz/readyz delay=0s timeout=1s period=10s #success=1 #failure=3 Environment: CLUSTER_API_OPENSTACK_INSTANCE_CREATE_TIMEOUT: 10 Mounts: /tmp/k8s-webhook-server/serving-certs from cert (ro) /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-42t4s (ro) Conditions: Type Status Initialized True Ready True ContainersReady True PodScheduled True Volumes: cert: Type: Secret (a volume populated by a Secret) SecretName: capo-webhook-service-cert Optional: false kube-api-access-42t4s: Type: Projected (a volume that contains injected data from multiple sources) TokenExpirationSeconds: 3607 ConfigMapName: kube-root-ca.crt ConfigMapOptional: DownwardAPI: true QoS Class: BestEffort Node-Selectors: openstack-control-plane=enabled Tolerations: node-role.kubernetes.io/control-plane:NoSchedule node-role.kubernetes.io/master:NoSchedule node.kubernetes.io/not-ready:NoExecute op=Exists for 300s node.kubernetes.io/unreachable:NoExecute op=Exists for 300s Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal Scheduled 33m default-scheduler Successfully assigned capo-system/capo-controller-manager-56cf844ccd-v9h2w to instance Normal Pulled 30m (x2 over 33m) kubelet Container image "harbor.atmosphere.dev/registry.k8s.io/capi-openstack/capi-openstack-controller:v0.14.4" already present on machine Normal Created 29m (x2 over 33m) kubelet Created container manager Normal Started 29m (x2 over 33m) kubelet Started container manager Warning Unhealthy 28m (x6 over 30m) kubelet Liveness probe failed: Get "http://10.0.0.14:9440/healthz": dial tcp 10.0.0.14:9440: connect: connection refused Normal Killing 28m (x4 over 30m) kubelet Container manager failed liveness probe, will be restarted Warning Unhealthy 28m (x10 over 30m) kubelet Readiness probe failed: Get "http://10.0.0.14:9440/readyz": dial tcp 10.0.0.14:9440: connect: connection refused