Name: capo-controller-manager-56cf844ccd-xqgsw Namespace: capo-system Priority: 0 Service Account: capo-manager Node: instance/199.204.45.95 Start Time: Tue, 07 Jul 2026 04:22:14 +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.49 IPs: IP: 10.0.0.49 Controlled By: ReplicaSet/capo-controller-manager-56cf844ccd Containers: manager: Container ID: containerd://8e5c38eb6ab7d0dad94916a7297e9a22671d61e576aa6ddc2b8a0594461dd66b 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, 07 Jul 2026 04:26:56 +0000 Last State: Terminated Reason: Error Message: ontrollerKind="OpenStackFloatingIPPool" I0707 04:22:27.714407 1 controller.go:289] "Starting workers" controller="openstackmachine" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackMachine" worker count=10 I0707 04:22:27.714422 1 controller.go:289] "Starting workers" controller="openstackfloatingippool" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackFloatingIPPool" worker count=1 I0707 04:22:27.714490 1 controller.go:286] "Starting Controller" controller="openstackcluster" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackCluster" I0707 04:22:27.714507 1 controller.go:289] "Starting workers" controller="openstackcluster" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackCluster" worker count=10 E0707 04:26:29.350230 1 leaderelection.go:441] Failed to update lock optimistically: the server was unable to return a response in the time allotted, but may still be processing the request (put leases.coordination.k8s.io controller-leader-election-capo), falling back to slow path E0707 04:26:34.348871 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 I0707 04:26:34.348928 1 leaderelection.go:297] failed to renew lease capo-system/controller-leader-election-capo: context deadline exceeded E0707 04:26:39.349413 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) E0707 04:26:39.349710 1 main.go:304] "problem running manager" err="leader election lost" logger="setup" I0707 04:26:39.349759 1 internal.go:555] "Stopping and waiting for non leader election runnables" Exit Code: 1 Started: Tue, 07 Jul 2026 04:22:15 +0000 Finished: Tue, 07 Jul 2026 04:26:54 +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-blhs5 (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-blhs5: 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 32m default-scheduler Successfully assigned capo-system/capo-controller-manager-56cf844ccd-xqgsw to instance Warning Unhealthy 27m kubelet Readiness probe failed: Get "http://10.0.0.49:9440/readyz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Warning Unhealthy 27m kubelet Liveness probe failed: Get "http://10.0.0.49:9440/healthz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Normal Pulled 27m (x2 over 32m) kubelet Container image "harbor.atmosphere.dev/registry.k8s.io/capi-openstack/capi-openstack-controller:v0.14.4" already present on machine Warning Unhealthy 27m kubelet Readiness probe failed: Get "http://10.0.0.49:9440/readyz": dial tcp 10.0.0.49:9440: connect: connection refused Warning Unhealthy 27m kubelet Liveness probe failed: Get "http://10.0.0.49:9440/healthz": dial tcp 10.0.0.49:9440: connect: connection refused Normal Created 27m (x2 over 32m) kubelet Created container manager Normal Started 27m (x2 over 32m) kubelet Started container manager