Name: capo-controller-manager-56cf844ccd-nzx9b Namespace: capo-system Priority: 0 Service Account: capo-manager Node: instance/199.204.45.72 Start Time: Tue, 30 Jun 2026 19:01:40 +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.30 IPs: IP: 10.0.0.30 Controlled By: ReplicaSet/capo-controller-manager-56cf844ccd Containers: manager: Container ID: containerd://962ff95af0f86e6abb9bbf7746656cfe555cdf80123a4a83503bd908821d23d5 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, 30 Jun 2026 19:08:05 +0000 Last State: Terminated Reason: Error Message: rKind="OpenStackFloatingIPPool" I0630 19:06:03.264052 1 controller.go:286] "Starting Controller" controller="openstackcluster" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackCluster" I0630 19:06:03.264057 1 controller.go:289] "Starting workers" controller="openstackcluster" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackCluster" worker count=10 I0630 19:06:03.264054 1 controller.go:289] "Starting workers" controller="openstackfloatingippool" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackFloatingIPPool" worker count=1 E0630 19:06:11.111838 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 E0630 19:07:13.048024 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 E0630 19:07:18.047906 1 leaderelection.go:484] Failed to update lock: 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 I0630 19:07:18.047962 1 leaderelection.go:297] failed to renew lease capo-system/controller-leader-election-capo: context deadline exceeded E0630 19:07:23.048662 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) E0630 19:07:23.048849 1 main.go:304] "problem running manager" err="leader election lost" logger="setup" Exit Code: 1 Started: Tue, 30 Jun 2026 19:06:02 +0000 Finished: Tue, 30 Jun 2026 19:07:41 +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-hr4lf (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-hr4lf: 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 39m default-scheduler Successfully assigned capo-system/capo-controller-manager-56cf844ccd-nzx9b to instance Warning Unhealthy 35m (x3 over 35m) kubelet Liveness probe failed: Get "http://10.0.0.30:9440/healthz": dial tcp 10.0.0.30:9440: connect: connection refused Normal Killing 35m (x3 over 35m) kubelet Container manager failed liveness probe, will be restarted Warning Unhealthy 35m (x9 over 35m) kubelet Readiness probe failed: Get "http://10.0.0.30:9440/readyz": dial tcp 10.0.0.30:9440: connect: connection refused Normal Pulled 34m (x2 over 39m) kubelet Container image "harbor.atmosphere.dev/registry.k8s.io/capi-openstack/capi-openstack-controller:v0.14.4" already present on machine Normal Created 34m (x2 over 39m) kubelet Created container manager Normal Started 34m (x2 over 39m) kubelet Started container manager Warning Unhealthy 33m kubelet Liveness probe failed: Get "http://10.0.0.30:9440/healthz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Warning Unhealthy 33m kubelet Readiness probe failed: Get "http://10.0.0.30:9440/readyz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Warning Unhealthy 33m kubelet Liveness probe failed: Get "http://10.0.0.30:9440/healthz": read tcp 10.0.0.155:60722->10.0.0.30:9440: read: connection reset by peer Warning Unhealthy 33m kubelet Readiness probe failed: Get "http://10.0.0.30:9440/readyz": read tcp 10.0.0.155:60724->10.0.0.30:9440: read: connection reset by peer Warning BackOff 33m kubelet Back-off restarting failed container manager in pod capo-controller-manager-56cf844ccd-nzx9b_capo-system(c4b213ab-9c93-4cc8-955d-b646a556e44e)