Name: capo-controller-manager-6975759b4b-f5ghd Namespace: capo-system Priority: 0 Service Account: capo-manager Node: instance/199.204.45.69 Start Time: Thu, 26 Feb 2026 02:32:42 +0000 Labels: cluster.x-k8s.io/provider=infrastructure-openstack control-plane=capo-controller-manager pod-template-hash=6975759b4b Annotations: Status: Running SeccompProfile: RuntimeDefault IP: 10.0.0.138 IPs: IP: 10.0.0.138 Controlled By: ReplicaSet/capo-controller-manager-6975759b4b Containers: manager: Container ID: containerd://0421920b77cb405a596f021c2297eb7b0d15c9437cd5f308c57cea31438404d8 Image: harbor.atmosphere.dev/registry.k8s.io/capi-openstack/capi-openstack-controller:v0.12.4 Image ID: harbor.atmosphere.dev/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, 26 Feb 2026 02:45:15 +0000 Last State: Terminated Reason: Error Message: x-k8s.io" controllerKind="OpenStackCluster" worker count=10 I0226 02:42:57.090571 1 controller.go:217] "Starting workers" controller="openstackmachine" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackMachine" worker count=10 I0226 02:42:57.884109 1 reflector.go:368] Caches populated for *v1alpha1.OpenStackFloatingIPPool from pkg/mod/k8s.io/client-go@v0.31.10/tools/cache/reflector.go:243 E0226 02:43:13.577332 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 I0226 02:43:14.053025 1 reflector.go:368] Caches populated for *v1alpha1.OpenStackServer from pkg/mod/k8s.io/client-go@v0.31.10/tools/cache/reflector.go:243 I0226 02:43:14.507650 1 reflector.go:368] Caches populated for *v1beta1.IPAddressClaim from pkg/mod/k8s.io/client-go@v0.31.10/tools/cache/reflector.go:243 I0226 02:43:17.469546 1 reflector.go:368] Caches populated for *v1beta1.IPAddress from pkg/mod/k8s.io/client-go@v0.31.10/tools/cache/reflector.go:243 E0226 02:43:18.578130 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 I0226 02:43:18.578190 1 leaderelection.go:297] failed to renew lease capo-system/controller-leader-election-capo: timed out waiting for the condition E0226 02:43:22.830331 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 E0226 02:43:22.830449 1 main.go:281] "problem running manager" err="leader election lost" logger="setup" Exit Code: 1 Started: Thu, 26 Feb 2026 02:38:57 +0000 Finished: Thu, 26 Feb 2026 02:43:22 +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-6b2p7 (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-6b2p7: 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-6975759b4b-f5ghd to instance Warning Unhealthy 38m kubelet Liveness probe failed: Get "http://10.0.0.138:9440/healthz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Warning Unhealthy 38m kubelet Readiness probe failed: Get "http://10.0.0.138:9440/readyz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Warning Unhealthy 38m (x2 over 38m) kubelet Liveness probe failed: Get "http://10.0.0.138:9440/healthz": dial tcp 10.0.0.138:9440: connect: connection refused Normal Killing 38m kubelet Container manager failed liveness probe, will be restarted Normal Pulled 38m (x2 over 41m) kubelet Container image "harbor.atmosphere.dev/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 36m (x16 over 38m) kubelet Readiness probe failed: Get "http://10.0.0.138:9440/readyz": dial tcp 10.0.0.138:9440: connect: connection refused