Name: capo-controller-manager-56cf844ccd-jt5ns Namespace: capo-system Priority: 0 Service Account: capo-manager Node: instance/199.19.213.86 Start Time: Tue, 14 Jul 2026 18:28:01 +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.29 IPs: IP: 10.0.0.29 Controlled By: ReplicaSet/capo-controller-manager-56cf844ccd Containers: manager: Container ID: containerd://79be4b998b37c76c52fa76f6a3aa2ca7fcc4dc3e67405c9c682556d8d957bc70 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 18:57:45 +0000 Last State: Terminated Reason: Error Message: rs" controller="openstackserver" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackServer" worker count=10 E0714 18:57:21.503829 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 18:57:26.503359 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 I0714 18:57:26.503417 1 leaderelection.go:297] failed to renew lease capo-system/controller-leader-election-capo: context deadline exceeded E0714 18:57:31.504118 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 I0714 18:57:31.504423 1 recorder.go:104] "capo-controller-manager-56cf844ccd-jt5ns_3f7c5684-d515-4849-92f3-694e88be534a stopped leading" logger="events" type="Normal" object={"kind":"Lease","namespace":"capo-system","name":"controller-leader-election-capo","uid":"5e001375-5ad6-471b-8298-42ec7e97bc6d","apiVersion":"coordination.k8s.io/v1","resourceVersion":"37783"} reason="LeaderElection" I0714 18:57:31.504698 1 internal.go:555] "Stopping and waiting for non leader election runnables" I0714 18:57:31.504730 1 internal.go:559] "Stopping and waiting for leader election runnables" E0714 18:57:31.504719 1 main.go:304] "problem running manager" err="leader election lost" logger="setup" I0714 18:57:31.504759 1 internal.go:567] "Stopping and waiting for caches" I0714 18:57:31.504819 1 internal.go:571] "Stopping and waiting for webhooks" Exit Code: 1 Started: Tue, 14 Jul 2026 18:28:02 +0000 Finished: Tue, 14 Jul 2026 18:57:31 +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-x9wn6 (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-x9wn6: 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 35m default-scheduler Successfully assigned capo-system/capo-controller-manager-56cf844ccd-jt5ns to instance Warning Unhealthy 5m25s (x2 over 5m35s) kubelet Readiness probe failed: Get "http://10.0.0.29:9440/readyz": dial tcp 10.0.0.29:9440: connect: connection refused Warning Unhealthy 5m25s (x2 over 5m35s) kubelet Liveness probe failed: Get "http://10.0.0.29:9440/healthz": dial tcp 10.0.0.29:9440: connect: connection refused Normal Pulled 5m24s (x2 over 35m) kubelet Container image "harbor.atmosphere.dev/registry.k8s.io/capi-openstack/capi-openstack-controller:v0.14.4" already present on machine Normal Created 5m22s (x2 over 35m) kubelet Created container manager Normal Started 5m21s (x2 over 35m) kubelet Started container manager