Name: capo-controller-manager-56cf844ccd-xs4x8 Namespace: capo-system Priority: 0 Service Account: capo-manager Node: instance/199.204.45.144 Start Time: Tue, 14 Jul 2026 23:51:14 +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.6 IPs: IP: 10.0.0.6 Controlled By: ReplicaSet/capo-controller-manager-56cf844ccd Containers: manager: Container ID: containerd://db34c85197e85c7d193fa5a6faed570a5556ede5adde24e6a1e17e28a76ddcbe 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: Tue, 14 Jul 2026 23:56:26 +0000 Last State: Terminated Reason: Error Message: luster" I0714 23:51:25.205816 1 controller.go:289] "Starting workers" controller="openstackcluster" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackCluster" worker count=10 E0714 23:54:11.596831 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 E0714 23:54:16.597234 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": net/http: request canceled (Client.Timeout exceeded while awaiting headers) I0714 23:54:16.597300 1 leaderelection.go:297] failed to renew lease capo-system/controller-leader-election-capo: context deadline exceeded E0714 23:54:21.598536 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 (Client.Timeout exceeded while awaiting headers) I0714 23:54:21.598922 1 recorder.go:104] "capo-controller-manager-56cf844ccd-xs4x8_1c24651c-c4b2-48bc-bf8d-6c3f6a022b14 stopped leading" logger="events" type="Normal" object={"kind":"Lease","namespace":"capo-system","name":"controller-leader-election-capo","uid":"21bed5e8-37f2-4acd-b4c6-19482014ccd3","apiVersion":"coordination.k8s.io/v1","resourceVersion":"27249"} reason="LeaderElection" I0714 23:54:21.598965 1 internal.go:555] "Stopping and waiting for non leader election runnables" I0714 23:54:21.599015 1 internal.go:550] "Stopping and waiting for warmup runnables" E0714 23:54:21.599014 1 main.go:304] "problem running manager" err="leader election lost" logger="setup" Exit Code: 1 Started: Tue, 14 Jul 2026 23:51:15 +0000 Finished: Tue, 14 Jul 2026 23:54:21 +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-hx9t5 (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-hx9t5: 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 36m default-scheduler Successfully assigned capo-system/capo-controller-manager-56cf844ccd-xs4x8 to instance Normal Pulled 36m kubelet Container image "harbor.atmosphere.dev/registry.k8s.io/capi-openstack/capi-openstack-controller:v0.14.4" already present on machine Normal Created 36m kubelet Created container manager Normal Started 36m kubelet Started container manager Warning Unhealthy 33m (x3 over 33m) kubelet Liveness probe failed: Get "http://10.0.0.6:9440/healthz": dial tcp 10.0.0.6:9440: connect: connection refused Warning Unhealthy 32m (x14 over 33m) kubelet Readiness probe failed: Get "http://10.0.0.6:9440/readyz": dial tcp 10.0.0.6:9440: connect: connection refused Normal Killing 32m (x6 over 33m) kubelet Container manager failed liveness probe, will be restarted