Name: capo-controller-manager-666756b48-m4zdd Namespace: capo-system Priority: 0 Service Account: capo-manager Node: instance/199.204.45.70 Start Time: Thu, 19 Feb 2026 19:48:04 +0000 Labels: cluster.x-k8s.io/provider=infrastructure-openstack control-plane=capo-controller-manager pod-template-hash=666756b48 Annotations: Status: Running SeccompProfile: RuntimeDefault IP: 172.24.0.28 IPs: IP: 172.24.0.28 Controlled By: ReplicaSet/capo-controller-manager-666756b48 Containers: manager: Container ID: containerd://07b31c1b7a5038df7a981302471f4b412e624ef901cc596bfb6676c91a2d078e Image: registry.k8s.io/capi-openstack/capi-openstack-controller:v0.12.4 Image ID: registry.k8s.io/capi-openstack/capi-openstack-controller@sha256:237da708e483aa8c39766a217d25e45de52816d446764569c77550e6f56f0970 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, 19 Feb 2026 19:54:14 +0000 Last State: Terminated Reason: Error Message: 55360 1 reflector.go:368] Caches populated for *v1alpha1.Image from pkg/mod/k8s.io/client-go@v0.31.10/tools/cache/reflector.go:243 I0219 19:52:32.846710 1 controller.go:217] "Starting workers" controller="openstackfloatingippool" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackFloatingIPPool" worker count=1 I0219 19:52:32.849289 1 controller.go:217] "Starting workers" controller="openstackcluster" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackCluster" worker count=10 I0219 19:52:32.853537 1 controller.go:217] "Starting workers" controller="openstackmachine" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackMachine" worker count=10 I0219 19:52:32.853581 1 controller.go:217] "Starting workers" controller="openstackserver" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackServer" worker count=10 E0219 19:52:46.012328 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 E0219 19:52:51.012430 1 leaderelection.go:436] error retrieving resource lock capo-system/controller-leader-election-capo: Get "https://10.96.0.1:443/apis/coordination.k8s.io/v1/namespaces/capo-system/leases/controller-leader-election-capo?timeout=5s": context deadline exceeded I0219 19:52:51.012512 1 leaderelection.go:297] failed to renew lease capo-system/controller-leader-election-capo: timed out waiting for the condition E0219 19:52:56.013236 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) E0219 19:52:56.013335 1 main.go:281] "problem running manager" err="leader election lost" logger="setup" Exit Code: 1 Started: Thu, 19 Feb 2026 19:52:17 +0000 Finished: Thu, 19 Feb 2026 19:52:56 +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-bcn29 (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-bcn29: 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 41m default-scheduler Successfully assigned capo-system/capo-controller-manager-666756b48-m4zdd to instance Normal Pulled 37m (x2 over 41m) kubelet Container image "registry.k8s.io/capi-openstack/capi-openstack-controller:v0.12.4" already present on machine Normal Created 36m (x2 over 41m) kubelet Created container manager Normal Started 36m (x2 over 41m) kubelet Started container manager Warning Unhealthy 35m (x6 over 37m) kubelet Liveness probe failed: Get "http://172.24.0.28:9440/healthz": dial tcp 172.24.0.28:9440: connect: connection refused Normal Killing 35m (x2 over 37m) kubelet Container manager failed liveness probe, will be restarted Warning Unhealthy 35m (x12 over 37m) kubelet Readiness probe failed: Get "http://172.24.0.28:9440/readyz": dial tcp 172.24.0.28:9440: connect: connection refused