Name: capo-controller-manager-56cf844ccd-dctv9 Namespace: capo-system Priority: 0 Service Account: capo-manager Node: instance/199.204.45.78 Start Time: Wed, 24 Jun 2026 19:00:07 +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.204 IPs: IP: 10.0.0.204 Controlled By: ReplicaSet/capo-controller-manager-56cf844ccd Containers: manager: Container ID: containerd://12e80e1cd50666f14dda1ee0dd62f0d9737906c1e28399688c2e9bb5045979ad 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: Wed, 24 Jun 2026 19:13:09 +0000 Last State: Terminated Reason: Error Message: e" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackMachine" I0624 19:04:46.012353 1 controller.go:289] "Starting workers" controller="openstackmachine" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackMachine" worker count=10 E0624 19:04:52.909630 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 E0624 19:05:40.974059 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 E0624 19:12:11.238687 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 E0624 19:12:16.238879 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 I0624 19:12:16.238942 1 leaderelection.go:297] failed to renew lease capo-system/controller-leader-election-capo: context deadline exceeded E0624 19:12:21.239868 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) E0624 19:12:21.245195 1 main.go:304] "problem running manager" err="leader election lost" logger="setup" Exit Code: 1 Started: Wed, 24 Jun 2026 19:04:45 +0000 Finished: Wed, 24 Jun 2026 19:12:21 +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-lbpvm (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-lbpvm: 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 46m default-scheduler Successfully assigned capo-system/capo-controller-manager-56cf844ccd-dctv9 to instance Normal Created 41m (x2 over 46m) kubelet Created container manager Normal Started 41m (x2 over 46m) kubelet Started container manager Normal Pulled 33m (x3 over 46m) kubelet Container image "harbor.atmosphere.dev/registry.k8s.io/capi-openstack/capi-openstack-controller:v0.14.4" already present on machine Warning Unhealthy 33m (x11 over 42m) kubelet Readiness probe failed: Get "http://10.0.0.204:9440/readyz": dial tcp 10.0.0.204:9440: connect: connection refused Warning Unhealthy 33m (x6 over 42m) kubelet Liveness probe failed: Get "http://10.0.0.204:9440/healthz": dial tcp 10.0.0.204:9440: connect: connection refused Normal Killing 33m (x3 over 42m) kubelet Container manager failed liveness probe, will be restarted