Name: capo-controller-manager-65565fdb7f-r4x4n Namespace: capo-system Priority: 0 Service Account: capo-manager Node: instance/199.204.45.132 Start Time: Tue, 05 May 2026 23:02:07 +0000 Labels: cluster.x-k8s.io/provider=infrastructure-openstack control-plane=capo-controller-manager pod-template-hash=65565fdb7f Annotations: Status: Running SeccompProfile: RuntimeDefault IP: 10.0.0.154 IPs: IP: 10.0.0.154 Controlled By: ReplicaSet/capo-controller-manager-65565fdb7f Containers: manager: Container ID: containerd://c461857140a49eb199c653dc2788a2fec585083eeee3929bd6ee82dc44b8b79e Image: harbor.atmosphere.dev/registry.k8s.io/capi-openstack/capi-openstack-controller:v0.12.7 Image ID: harbor.atmosphere.dev/registry.k8s.io/capi-openstack/capi-openstack-controller@sha256:b964c2f374ad4f26a593749d3c737492d5c1821db143b26596c9285b9055a8b4 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 State: Running Started: Tue, 05 May 2026 23:06:43 +0000 Last State: Terminated Reason: Error Message: ngIPPool" worker count=1 I0505 23:06:05.544081 1 controller.go:217] "Starting workers" controller="openstackmachine" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackMachine" worker count=10 E0505 23:06:12.461496 1 leaderelection.go:429] Failed to update lock optimitically: Put "https://10.96.0.1:443/apis/coordination.k8s.io/v1/namespaces/capo-system/leases/controller-leader-election-capo?timeout=5s": net/http: request canceled (Client.Timeout exceeded while awaiting headers), falling back to slow path E0505 23:06:17.461198 1 leaderelection.go:472] 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 I0505 23:06:17.461278 1 leaderelection.go:297] failed to renew lease capo-system/controller-leader-election-capo: timed out waiting for the condition I0505 23:06:19.131075 1 internal.go:538] "Stopping and waiting for non leader election runnables" I0505 23:06:19.131115 1 internal.go:542] "Stopping and waiting for leader election runnables" I0505 23:06:19.131138 1 internal.go:550] "Stopping and waiting for caches" I0505 23:06:19.131154 1 internal.go:554] "Stopping and waiting for webhooks" I0505 23:06:19.131163 1 internal.go:557] "Stopping and waiting for HTTP servers" I0505 23:06:19.131171 1 internal.go:561] "Wait completed, proceeding to shutdown the manager" I0505 23:06:19.131185 1 controller.go:237] "Shutdown signal received, waiting for all workers to finish" controller="openstackserver" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackServer" I0505 23:06:19.131176 1 controller.go:237] "Shutdown signal received, waiting for all workers to finish" controller="openstackcluster" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackCluster" E0505 23:06:19.131028 1 main.go:281] "problem running manager" err="leader election lost" logger="setup" Exit Code: 1 Started: Tue, 05 May 2026 23:06:04 +0000 Finished: Tue, 05 May 2026 23:06:19 +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-prmq5 (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-prmq5: 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 31m default-scheduler Successfully assigned capo-system/capo-controller-manager-65565fdb7f-r4x4n to instance Warning Unhealthy 27m kubelet Liveness probe failed: Get "http://10.0.0.154:9440/healthz": dial tcp 10.0.0.154:9440: connect: connection refused Warning Unhealthy 27m kubelet Readiness probe failed: Get "http://10.0.0.154:9440/readyz": dial tcp 10.0.0.154:9440: connect: connection refused Warning BackOff 26m (x3 over 26m) kubelet Back-off restarting failed container manager in pod capo-controller-manager-65565fdb7f-r4x4n_capo-system(d715c808-d0d1-45ff-8ee0-d7119e44cae3) Normal Pulled 26m (x3 over 31m) kubelet Container image "harbor.atmosphere.dev/registry.k8s.io/capi-openstack/capi-openstack-controller:v0.12.7" already present on machine Normal Created 26m (x3 over 31m) kubelet Created container manager Normal Started 26m (x3 over 31m) kubelet Started container manager