Name: capo-controller-manager-666756b48-4rx2m Namespace: capo-system Priority: 0 Service Account: capo-manager Node: instance/162.253.55.227 Start Time: Thu, 19 Feb 2026 06:10:07 +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.188 IPs: IP: 172.24.0.188 Controlled By: ReplicaSet/capo-controller-manager-666756b48 Containers: manager: Container ID: containerd://4675076ea1d6eb1c0528db9d9d5efc6ee10fa76c25f9b27adfd82d07e4af8055 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 06:14:54 +0000 Last State: Terminated Reason: Error Message: nStackMachine" worker count=10 I0219 06:10:18.070528 1 controller.go:217] "Starting workers" controller="openstackcluster" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackCluster" worker count=10 I0219 06:10:18.070517 1 controller.go:217] "Starting workers" controller="openstackserver" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackServer" worker count=10 I0219 06:10:18.070606 1 controller.go:217] "Starting workers" controller="openstackfloatingippool" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackFloatingIPPool" worker count=1 E0219 06:13:41.415602 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 06:14:16.143213 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 E0219 06:14:21.142736 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 06:14:21.142817 1 leaderelection.go:297] failed to renew lease capo-system/controller-leader-election-capo: timed out waiting for the condition E0219 06:14:26.077426 1 leaderelection.go:322] Failed to release lock: Operation cannot be fulfilled on leases.coordination.k8s.io "controller-leader-election-capo": the object has been modified; please apply your changes to the latest version and try again E0219 06:14:26.077498 1 main.go:281] "problem running manager" err="leader election lost" logger="setup" Exit Code: 1 Started: Thu, 19 Feb 2026 06:10:08 +0000 Finished: Thu, 19 Feb 2026 06:14:32 +0000 Ready: True Restart Count: 1 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-pctmb (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-pctmb: 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 22m default-scheduler Successfully assigned capo-system/capo-controller-manager-666756b48-4rx2m to instance Warning Unhealthy 18m kubelet Readiness probe failed: Get "http://172.24.0.188:9440/readyz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Warning Unhealthy 18m kubelet Liveness probe failed: Get "http://172.24.0.188:9440/healthz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Normal Pulled 18m (x2 over 22m) kubelet Container image "registry.k8s.io/capi-openstack/capi-openstack-controller:v0.12.4" already present on machine Warning Unhealthy 18m (x3 over 18m) kubelet Readiness probe failed: Get "http://172.24.0.188:9440/readyz": dial tcp 172.24.0.188:9440: connect: connection refused Warning Unhealthy 18m (x2 over 18m) kubelet Liveness probe failed: Get "http://172.24.0.188:9440/healthz": dial tcp 172.24.0.188:9440: connect: connection refused Normal Killing 18m kubelet Container manager failed liveness probe, will be restarted Normal Created 18m (x2 over 22m) kubelet Created container manager Normal Started 18m (x2 over 22m) kubelet Started container manager