Name: capo-controller-manager-65565fdb7f-89jqb Namespace: capo-system Priority: 0 Service Account: capo-manager Node: instance/199.19.213.74 Start Time: Thu, 23 Apr 2026 10:19:35 +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.11 IPs: IP: 10.0.0.11 Controlled By: ReplicaSet/capo-controller-manager-65565fdb7f Containers: manager: Container ID: containerd://c5a6654b63af87262b303ecc0da241b0602546a9424fcdf28d9543cdd2365658 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, 23 Apr 2026 10:30:37 +0000 Last State: Terminated Reason: Error Message: .882946 1 reflector.go:368] Caches populated for *v1alpha1.Image from pkg/mod/k8s.io/client-go@v0.31.14/tools/cache/reflector.go:243 I0423 10:25:35.883288 1 reflector.go:368] Caches populated for *v1alpha1.OpenStackFloatingIPPool from pkg/mod/k8s.io/client-go@v0.31.14/tools/cache/reflector.go:243 I0423 10:25:35.884379 1 reflector.go:368] Caches populated for *v1beta1.OpenStackMachine from pkg/mod/k8s.io/client-go@v0.31.14/tools/cache/reflector.go:243 I0423 10:25:35.980009 1 controller.go:217] "Starting workers" controller="openstackcluster" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackCluster" worker count=10 I0423 10:25:35.983424 1 controller.go:217] "Starting workers" controller="openstackmachine" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackMachine" worker count=10 I0423 10:25:35.983430 1 controller.go:217] "Starting workers" controller="openstackfloatingippool" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackFloatingIPPool" worker count=1 I0423 10:25:35.982403 1 controller.go:217] "Starting workers" controller="openstackserver" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackServer" worker count=10 E0423 10:30:12.660472 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 E0423 10:30:17.659730 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 I0423 10:30:17.659798 1 leaderelection.go:297] failed to renew lease capo-system/controller-leader-election-capo: timed out waiting for the condition E0423 10:30:18.427710 1 main.go:281] "problem running manager" err="leader election lost" logger="setup" Exit Code: 1 Started: Thu, 23 Apr 2026 10:25:19 +0000 Finished: Thu, 23 Apr 2026 10:30:18 +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-8v2n7 (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-8v2n7: 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 30m default-scheduler Successfully assigned capo-system/capo-controller-manager-65565fdb7f-89jqb to instance Warning Unhealthy 26m (x3 over 26m) kubelet Liveness probe failed: Get "http://10.0.0.11:9440/healthz": dial tcp 10.0.0.11:9440: connect: connection refused Normal Killing 26m kubelet Container manager failed liveness probe, will be restarted Warning Unhealthy 26m (x4 over 26m) kubelet Readiness probe failed: Get "http://10.0.0.11:9440/readyz": dial tcp 10.0.0.11:9440: connect: connection refused Warning Unhealthy 24m kubelet Liveness probe failed: Get "http://10.0.0.11:9440/healthz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Warning Unhealthy 24m kubelet Readiness probe failed: Get "http://10.0.0.11:9440/readyz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Warning BackOff 19m (x3 over 19m) kubelet Back-off restarting failed container manager in pod capo-controller-manager-65565fdb7f-89jqb_capo-system(9409b54c-b460-40c2-b955-ba9197f2f26b) Normal Pulled 19m (x4 over 30m) kubelet Container image "harbor.atmosphere.dev/registry.k8s.io/capi-openstack/capi-openstack-controller:v0.12.7" already present on machine Normal Created 19m (x4 over 30m) kubelet Created container manager Normal Started 19m (x4 over 30m) kubelet Started container manager