Name: capo-controller-manager-56cf844ccd-jh5bf Namespace: capo-system Priority: 0 Service Account: capo-manager Node: instance/199.204.45.44 Start Time: Thu, 13 Aug 2026 01:39:46 +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.115 IPs: IP: 10.0.0.115 Controlled By: ReplicaSet/capo-controller-manager-56cf844ccd Containers: manager: Container ID: containerd://ac7eabbe8e57a61b372534278103bb4147cf0413ea17954060b3a38ed972a7b5 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: Thu, 13 Aug 2026 01:43:19 +0000 Last State: Terminated Reason: Error Message: oatingIPPool" worker count=1 I0813 01:39:57.024145 1 controller.go:286] "Starting Controller" controller="openstackcluster" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackCluster" I0813 01:39:57.024172 1 controller.go:289] "Starting workers" controller="openstackcluster" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackCluster" worker count=10 I0813 01:39:57.024219 1 controller.go:286] "Starting Controller" controller="openstackmachine" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackMachine" I0813 01:39:57.024243 1 controller.go:289] "Starting workers" controller="openstackmachine" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackMachine" worker count=10 E0813 01:42:41.225007 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 E0813 01:42:46.225522 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) E0813 01:42:46.225637 1 leaderelection.go:441] Failed to update lock optimistically: client rate limiter Wait returned an error: context deadline exceeded, falling back to slow path E0813 01:42:46.225661 1 leaderelection.go:448] error retrieving resource lock capo-system/controller-leader-election-capo: client rate limiter Wait returned an error: context deadline exceeded I0813 01:42:46.225680 1 leaderelection.go:297] failed to renew lease capo-system/controller-leader-election-capo: context deadline exceeded E0813 01:42:51.145147 1 main.go:304] "problem running manager" err="leader election lost" logger="setup" Exit Code: 1 Started: Thu, 13 Aug 2026 01:39:47 +0000 Finished: Thu, 13 Aug 2026 01:42:51 +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-h62qm (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-h62qm: 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 6m47s default-scheduler Successfully assigned capo-system/capo-controller-manager-56cf844ccd-jh5bf to instance Normal Pulled 3m17s (x2 over 6m47s) kubelet Container image "harbor.atmosphere.dev/registry.k8s.io/capi-openstack/capi-openstack-controller:v0.14.4" already present on machine Warning Unhealthy 3m17s (x4 over 3m37s) kubelet Readiness probe failed: Get "http://10.0.0.115:9440/readyz": dial tcp 10.0.0.115:9440: connect: connection refused Warning Unhealthy 3m17s (x3 over 3m37s) kubelet Liveness probe failed: Get "http://10.0.0.115:9440/healthz": dial tcp 10.0.0.115:9440: connect: connection refused Normal Killing 3m17s kubelet Container manager failed liveness probe, will be restarted Normal Created 3m15s (x2 over 6m47s) kubelet Created container manager Normal Started 3m14s (x2 over 6m46s) kubelet Started container manager