Name: capo-controller-manager-65565fdb7f-smgsq Namespace: capo-system Priority: 0 Service Account: capo-manager Node: instance/199.19.213.231 Start Time: Thu, 21 May 2026 05:52:56 +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.231 IPs: IP: 10.0.0.231 Controlled By: ReplicaSet/capo-controller-manager-65565fdb7f Containers: manager: Container ID: containerd://2dda0b966861aefecd9a995d5c49d2e68506cd2355497fdb789ed7acebc2ec51 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: Thu, 21 May 2026 06:10:32 +0000 Last State: Terminated Reason: Error Message: ter.x-k8s.io" controllerKind="OpenStackServer" worker count=10 I0521 06:01:32.486774 1 controller.go:217] "Starting workers" controller="openstackcluster" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackCluster" worker count=10 I0521 06:01:32.486799 1 controller.go:217] "Starting workers" controller="openstackfloatingippool" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackFloatingIPPool" worker count=1 I0521 06:01:32.486904 1 controller.go:217] "Starting workers" controller="openstackmachine" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackMachine" worker count=10 E0521 06:09:14.797032 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 E0521 06:09:51.548373 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": context deadline exceeded, falling back to slow path E0521 06:09:56.549835 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 I0521 06:09:56.549912 1 leaderelection.go:297] failed to renew lease capo-system/controller-leader-election-capo: timed out waiting for the condition E0521 06:10:01.550464 1 leaderelection.go:322] Failed to release lock: 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) E0521 06:10:01.550622 1 main.go:281] "problem running manager" err="leader election lost" logger="setup" Exit Code: 1 Started: Thu, 21 May 2026 06:01:15 +0000 Finished: Thu, 21 May 2026 06:10:01 +0000 Ready: True Restart Count: 3 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-78ncd (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-78ncd: 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 48m default-scheduler Successfully assigned capo-system/capo-controller-manager-65565fdb7f-smgsq to instance Normal Pulled 42m (x2 over 48m) kubelet Container image "harbor.atmosphere.dev/registry.k8s.io/capi-openstack/capi-openstack-controller:v0.12.7" already present on machine Normal Created 42m (x2 over 48m) kubelet Created container manager Normal Started 42m (x2 over 48m) kubelet Started container manager Warning Unhealthy 40m (x6 over 43m) kubelet Liveness probe failed: Get "http://10.0.0.231:9440/healthz": dial tcp 10.0.0.231:9440: connect: connection refused Normal Killing 40m (x2 over 42m) kubelet Container manager failed liveness probe, will be restarted Warning Unhealthy 40m (x12 over 43m) kubelet Readiness probe failed: Get "http://10.0.0.231:9440/readyz": dial tcp 10.0.0.231:9440: connect: connection refused Warning BackOff 31m (x2 over 31m) kubelet Back-off restarting failed container manager in pod capo-controller-manager-65565fdb7f-smgsq_capo-system(575212f8-ee57-488d-a288-542a7e9505e1)