Name: capo-controller-manager-56cf844ccd-gg5hl Namespace: capo-system Priority: 0 Service Account: capo-manager Node: instance/199.204.45.74 Start Time: Mon, 24 Aug 2026 16:30:18 +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.140 IPs: IP: 10.0.0.140 Controlled By: ReplicaSet/capo-controller-manager-56cf844ccd Containers: manager: Container ID: containerd://ea06850a692dd7f4f3bcf4f41941992846fceb0457276d6aee112ed8397aea3d 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: Mon, 24 Aug 2026 16:39:04 +0000 Last State: Terminated Reason: Error Message: re.cluster.x-k8s.io" controllerKind="OpenStackMachine" worker count=10 I0824 16:30:24.304212 1 controller.go:286] "Starting Controller" controller="openstackserver" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackServer" I0824 16:30:24.304221 1 controller.go:289] "Starting workers" controller="openstackserver" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackServer" worker count=10 E0824 16:33:26.618557 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 E0824 16:33:31.617113 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 I0824 16:33:31.617186 1 leaderelection.go:297] failed to renew lease capo-system/controller-leader-election-capo: context deadline exceeded E0824 16:33:36.617982 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) E0824 16:33:36.618430 1 main.go:304] "problem running manager" err="leader election lost" logger="setup" I0824 16:33:36.618418 1 recorder.go:104] "capo-controller-manager-56cf844ccd-gg5hl_12cf2bda-42af-4a86-83b7-c87702abc80c stopped leading" logger="events" type="Normal" object={"kind":"Lease","namespace":"capo-system","name":"controller-leader-election-capo","uid":"b4b7553f-ef1b-4ddd-ada2-48b9900284b9","apiVersion":"coordination.k8s.io/v1","resourceVersion":"29189"} reason="LeaderElection" Exit Code: 1 Started: Mon, 24 Aug 2026 16:30:20 +0000 Finished: Mon, 24 Aug 2026 16:33:36 +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-t9xb4 (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-t9xb4: 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 43m default-scheduler Successfully assigned capo-system/capo-controller-manager-56cf844ccd-gg5hl to instance Normal Pulled 43m kubelet Container image "harbor.atmosphere.dev/registry.k8s.io/capi-openstack/capi-openstack-controller:v0.14.4" already present on machine Normal Created 43m kubelet Created container manager Normal Started 43m kubelet Started container manager Warning Unhealthy 39m (x3 over 39m) kubelet Liveness probe failed: Get "http://10.0.0.140:9440/healthz": dial tcp 10.0.0.140:9440: connect: connection refused Normal Killing 38m (x5 over 39m) kubelet Container manager failed liveness probe, will be restarted Warning Unhealthy 38m (x15 over 39m) kubelet Readiness probe failed: Get "http://10.0.0.140:9440/readyz": dial tcp 10.0.0.140:9440: connect: connection refused