Name: capo-controller-manager-65565fdb7f-qw6x2 Namespace: capo-system Priority: 0 Service Account: capo-manager Node: instance/199.19.213.83 Start Time: Wed, 20 May 2026 13:54:17 +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.58 IPs: IP: 10.0.0.58 Controlled By: ReplicaSet/capo-controller-manager-65565fdb7f Containers: manager: Container ID: containerd://e8cf5ecba48f3723732a4e134a3ec581ca48339c6f4e199ecfa2fcfe57cd689c 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: Wed, 20 May 2026 14:00:54 +0000 Last State: Terminated Reason: Error Message: :243 I0520 13:57:57.761349 1 reflector.go:368] Caches populated for *v1beta1.Cluster from pkg/mod/k8s.io/client-go@v0.31.14/tools/cache/reflector.go:243 I0520 13:57:57.851795 1 controller.go:217] "Starting workers" controller="openstackfloatingippool" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackFloatingIPPool" worker count=1 I0520 13:57:57.857199 1 controller.go:217] "Starting workers" controller="openstackserver" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackServer" worker count=10 I0520 13:57:57.858401 1 controller.go:217] "Starting workers" controller="openstackcluster" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackCluster" worker count=10 I0520 13:57:57.859492 1 controller.go:217] "Starting workers" controller="openstackmachine" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackMachine" worker count=10 E0520 13:58:23.706039 1 leaderelection.go:429] Failed to update lock optimitically: the server was unable to return a response in the time allotted, but may still be processing the request (put leases.coordination.k8s.io controller-leader-election-capo), falling back to slow path E0520 13:58:28.707457 1 leaderelection.go:436] error retrieving resource lock capo-system/controller-leader-election-capo: the server was unable to return a response in the time allotted, but may still be processing the request (get leases.coordination.k8s.io controller-leader-election-capo) I0520 13:58:28.707501 1 leaderelection.go:297] failed to renew lease capo-system/controller-leader-election-capo: timed out waiting for the condition E0520 13:58:33.708643 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 E0520 13:58:33.708729 1 main.go:281] "problem running manager" err="leader election lost" logger="setup" Exit Code: 1 Started: Wed, 20 May 2026 13:57:57 +0000 Finished: Wed, 20 May 2026 13:59:09 +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-mks9x (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-mks9x: 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 34m default-scheduler Successfully assigned capo-system/capo-controller-manager-65565fdb7f-qw6x2 to instance Warning Unhealthy 31m (x3 over 31m) kubelet Liveness probe failed: Get "http://10.0.0.58:9440/healthz": dial tcp 10.0.0.58:9440: connect: connection refused Normal Pulled 30m (x2 over 34m) kubelet Container image "harbor.atmosphere.dev/registry.k8s.io/capi-openstack/capi-openstack-controller:v0.12.7" already present on machine Normal Created 30m (x2 over 34m) kubelet Created container manager Normal Started 30m (x2 over 34m) kubelet Started container manager Normal Killing 29m (x2 over 31m) kubelet Container manager failed liveness probe, will be restarted Warning Unhealthy 29m (x3 over 30m) kubelet Liveness probe failed: Get "http://10.0.0.58:9440/healthz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Warning Unhealthy 29m (x5 over 30m) kubelet Readiness probe failed: Get "http://10.0.0.58:9440/readyz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Warning Unhealthy 29m (x7 over 31m) kubelet Readiness probe failed: Get "http://10.0.0.58:9440/readyz": dial tcp 10.0.0.58:9440: connect: connection refused