Name: capo-controller-manager-56cf844ccd-2ck8z Namespace: capo-system Priority: 0 Service Account: capo-manager Node: instance/199.204.45.169 Start Time: Sat, 27 Jun 2026 09:42:37 +0000 Labels: cluster.x-k8s.io/provider=infrastructure-openstack control-plane=capo-controller-manager pod-template-hash=56cf844ccd Annotations: Status: Running SeccompProfile: RuntimeDefault IP: 10.0.0.12 IPs: IP: 10.0.0.12 Controlled By: ReplicaSet/capo-controller-manager-56cf844ccd Containers: manager: Container ID: containerd://e937fa4b6107ec6e350d03a6cb4103b61f276c3e6b5fb8610b99b4c233df9cb2 Image: harbor.atmosphere.dev/registry.k8s.io/capi-openstack/capi-openstack-controller:v0.14.4 Image ID: harbor.atmosphere.dev/registry.k8s.io/capi-openstack/capi-openstack-controller@sha256:b428de23d97c69ebb350e2359e73eb6ec92572e5dfab8cc4cea9994c01fa4ee0 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 --feature-gates=PriorityQueue=false,AutoScaleFromZero=false State: Running Started: Sat, 27 Jun 2026 09:47:08 +0000 Last State: Terminated Reason: Error Message: ckcluster" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackCluster" I0627 09:42:42.142902 1 controller.go:289] "Starting workers" controller="openstackcluster" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackCluster" worker count=10 I0627 09:42:42.142931 1 controller.go:286] "Starting Controller" controller="openstackmachine" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackMachine" I0627 09:42:42.142965 1 controller.go:289] "Starting workers" controller="openstackmachine" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackMachine" worker count=10 E0627 09:45:51.608358 1 leaderelection.go:441] Failed to update lock optimistically: 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 E0627 09:46:29.944106 1 leaderelection.go:441] Failed to update lock optimistically: 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 E0627 09:46:34.945400 1 leaderelection.go:484] 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 I0627 09:46:34.945465 1 leaderelection.go:297] failed to renew lease capo-system/controller-leader-election-capo: context deadline exceeded E0627 09:46:39.946244 1 leaderelection.go:316] 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 E0627 09:46:39.946368 1 main.go:304] "problem running manager" err="leader election lost" logger="setup" Exit Code: 1 Started: Sat, 27 Jun 2026 09:42:38 +0000 Finished: Sat, 27 Jun 2026 09:46:49 +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-8kbc4 (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-8kbc4: 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 32m default-scheduler Successfully assigned capo-system/capo-controller-manager-56cf844ccd-2ck8z to instance Warning Unhealthy 28m kubelet Liveness probe failed: Get "http://10.0.0.12:9440/healthz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Warning Unhealthy 28m kubelet Readiness probe failed: Get "http://10.0.0.12:9440/readyz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Warning Unhealthy 28m (x2 over 28m) kubelet Liveness probe failed: Get "http://10.0.0.12:9440/healthz": dial tcp 10.0.0.12:9440: connect: connection refused Normal Killing 28m kubelet Container manager failed liveness probe, will be restarted Normal Pulled 28m (x2 over 32m) kubelet Container image "harbor.atmosphere.dev/registry.k8s.io/capi-openstack/capi-openstack-controller:v0.14.4" already present on machine Normal Created 28m (x2 over 32m) kubelet Created container manager Normal Started 28m (x2 over 32m) kubelet Started container manager Warning Unhealthy 28m (x4 over 28m) kubelet Readiness probe failed: Get "http://10.0.0.12:9440/readyz": dial tcp 10.0.0.12:9440: connect: connection refused