Name: capo-controller-manager-56cf844ccd-lpbf7 Namespace: capo-system Priority: 0 Service Account: capo-manager Node: instance/199.19.213.133 Start Time: Thu, 02 Jul 2026 10:53:53 +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.86 IPs: IP: 10.0.0.86 Controlled By: ReplicaSet/capo-controller-manager-56cf844ccd Containers: manager: Container ID: containerd://9ddc4779164d6a1bafee19e81756bef772ec0fbfd7a8627bc2c87a567b219738 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: Thu, 02 Jul 2026 11:04:23 +0000 Last State: Terminated Reason: Error Message: StackMachine" I0702 10:58:44.046573 1 controller.go:289] "Starting workers" controller="openstackmachine" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackMachine" worker count=10 E0702 11:03:18.359774 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 E0702 11:03:27.932795 1 leaderelection.go:441] Failed to update lock optimistically: 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 E0702 11:03:32.932939 1 leaderelection.go:448] 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 I0702 11:03:32.932995 1 leaderelection.go:297] failed to renew lease capo-system/controller-leader-election-capo: context deadline exceeded E0702 11:03:37.934456 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": net/http: request canceled (Client.Timeout exceeded while awaiting headers) I0702 11:03:37.935762 1 recorder.go:104] "capo-controller-manager-56cf844ccd-lpbf7_da01da55-3289-4d29-b587-19a034484f41 stopped leading" logger="events" type="Normal" object={"kind":"Lease","namespace":"capo-system","name":"controller-leader-election-capo","uid":"a82846de-34a9-4cf5-8fa7-9177c6f53a75","apiVersion":"coordination.k8s.io/v1","resourceVersion":"28058"} reason="LeaderElection" E0702 11:03:37.935894 1 main.go:304] "problem running manager" err="leader election lost" logger="setup" Exit Code: 1 Started: Thu, 02 Jul 2026 10:58:43 +0000 Finished: Thu, 02 Jul 2026 11:03:37 +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-2nnct (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-2nnct: 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 38m default-scheduler Successfully assigned capo-system/capo-controller-manager-56cf844ccd-lpbf7 to instance Normal Created 33m (x2 over 38m) kubelet Created container manager Normal Started 33m (x2 over 38m) kubelet Started container manager Warning Unhealthy 28m (x6 over 34m) kubelet Liveness probe failed: Get "http://10.0.0.86:9440/healthz": dial tcp 10.0.0.86:9440: connect: connection refused Normal Pulled 28m (x3 over 38m) kubelet Container image "harbor.atmosphere.dev/registry.k8s.io/capi-openstack/capi-openstack-controller:v0.14.4" already present on machine Warning Unhealthy 28m (x10 over 34m) kubelet Readiness probe failed: Get "http://10.0.0.86:9440/readyz": dial tcp 10.0.0.86:9440: connect: connection refused Normal Killing 28m (x4 over 33m) kubelet Container manager failed liveness probe, will be restarted