Name: capo-controller-manager-65565fdb7f-jt92p Namespace: capo-system Priority: 0 Service Account: capo-manager Node: instance/199.204.45.153 Start Time: Tue, 19 May 2026 17:07:23 +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.180 IPs: IP: 10.0.0.180 Controlled By: ReplicaSet/capo-controller-manager-65565fdb7f Containers: manager: Container ID: containerd://75f01de96331e3269f0db30bba368d9a33f82a5114972008b06124f5c6f687aa 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: Tue, 19 May 2026 17:31:53 +0000 Last State: Terminated Reason: Error Message: /cache/reflector.go:243 I0519 17:31:07.824292 1 reflector.go:368] Caches populated for *v1beta1.OpenStackCluster from pkg/mod/k8s.io/client-go@v0.31.14/tools/cache/reflector.go:243 I0519 17:31:07.906119 1 controller.go:217] "Starting workers" controller="openstackfloatingippool" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackFloatingIPPool" worker count=1 I0519 17:31:07.921694 1 controller.go:217] "Starting workers" controller="openstackcluster" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackCluster" worker count=10 I0519 17:31:07.921864 1 controller.go:217] "Starting workers" controller="openstackserver" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackServer" worker count=10 I0519 17:31:07.923236 1 controller.go:217] "Starting workers" controller="openstackmachine" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackMachine" worker count=10 E0519 17:31:28.800164 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 E0519 17:31:33.800057 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 I0519 17:31:33.800127 1 leaderelection.go:297] failed to renew lease capo-system/controller-leader-election-capo: timed out waiting for the condition E0519 17:31:38.801495 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": context deadline exceeded E0519 17:31:38.801631 1 main.go:281] "problem running manager" err="leader election lost" logger="setup" Exit Code: 1 Started: Tue, 19 May 2026 17:30:50 +0000 Finished: Tue, 19 May 2026 17:31:38 +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-67tl8 (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-67tl8: 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-jt92p to instance Normal Killing 26m kubelet Container manager failed liveness probe, will be restarted Normal Pulled 7m38s (x3 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 7m25s (x3 over 30m) kubelet Created container manager Normal Started 7m24s (x3 over 30m) kubelet Started container manager Warning Unhealthy 6m31s (x4 over 26m) kubelet Liveness probe failed: Get "http://10.0.0.180:9440/healthz": dial tcp 10.0.0.180:9440: connect: connection refused Warning Unhealthy 6m31s (x14 over 26m) kubelet Readiness probe failed: Get "http://10.0.0.180:9440/readyz": dial tcp 10.0.0.180:9440: connect: connection refused Warning BackOff 6m30s kubelet Back-off restarting failed container manager in pod capo-controller-manager-65565fdb7f-jt92p_capo-system(ef7b7714-a722-4e92-b526-362bd6cb7a7a)