Name: capo-controller-manager-56cf844ccd-ncbqw Namespace: capo-system Priority: 0 Service Account: capo-manager Node: instance/199.204.45.138 Start Time: Fri, 24 Jul 2026 18:13:08 +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.135 IPs: IP: 10.0.0.135 Controlled By: ReplicaSet/capo-controller-manager-56cf844ccd Containers: manager: Container ID: containerd://d593fe5aedceee971b0f86b74c1210599e39403fed0568b6befe9f9f4795e8d8 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: Fri, 24 Jul 2026 18:18:17 +0000 Last State: Terminated Reason: Error Message: penStackServer" worker count=10 I0724 18:17:08.708425 1 controller.go:286] "Starting Controller" controller="openstackcluster" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackCluster" I0724 18:17:08.708444 1 controller.go:289] "Starting workers" controller="openstackcluster" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackCluster" worker count=10 I0724 18:17:08.708685 1 controller.go:286] "Starting Controller" controller="openstackmachine" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackMachine" I0724 18:17:08.708720 1 controller.go:289] "Starting workers" controller="openstackmachine" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackMachine" worker count=10 E0724 18:17:21.133688 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 E0724 18:17:26.134155 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 (Client.Timeout exceeded while awaiting headers) I0724 18:17:26.134229 1 leaderelection.go:297] failed to renew lease capo-system/controller-leader-election-capo: context deadline exceeded E0724 18:17:31.135462 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) E0724 18:17:31.135629 1 main.go:304] "problem running manager" err="leader election lost" logger="setup" Exit Code: 1 Started: Fri, 24 Jul 2026 18:16:44 +0000 Finished: Fri, 24 Jul 2026 18:17:49 +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-x5hmp (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-x5hmp: 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 40m default-scheduler Successfully assigned capo-system/capo-controller-manager-56cf844ccd-ncbqw to instance Normal Pulled 36m (x2 over 40m) kubelet Container image "harbor.atmosphere.dev/registry.k8s.io/capi-openstack/capi-openstack-controller:v0.14.4" already present on machine Normal Created 36m (x2 over 40m) kubelet Created container manager Normal Started 36m (x2 over 40m) kubelet Started container manager Warning Unhealthy 35m kubelet Liveness probe failed: Get "http://10.0.0.135:9440/healthz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Warning Unhealthy 35m kubelet Readiness probe failed: Get "http://10.0.0.135:9440/readyz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Warning Unhealthy 35m (x5 over 37m) kubelet Liveness probe failed: Get "http://10.0.0.135:9440/healthz": dial tcp 10.0.0.135:9440: connect: connection refused Normal Killing 35m (x3 over 36m) kubelet Container manager failed liveness probe, will be restarted Warning Unhealthy 34m (x10 over 37m) kubelet Readiness probe failed: Get "http://10.0.0.135:9440/readyz": dial tcp 10.0.0.135:9440: connect: connection refused