Name: capo-controller-manager-65565fdb7f-sng5l Namespace: capo-system Priority: 0 Service Account: capo-manager Node: instance/199.204.45.70 Start Time: Wed, 03 Jun 2026 00:38:14 +0000 Labels: cluster.x-k8s.io/provider=infrastructure-openstack control-plane=capo-controller-manager pod-template-hash=65565fdb7f Annotations: Status: Running SeccompProfile: RuntimeDefault IP: 10.0.0.88 IPs: IP: 10.0.0.88 Controlled By: ReplicaSet/capo-controller-manager-65565fdb7f Containers: manager: Container ID: containerd://4385c3c2c7b2518c8f253e89c0327a7a13499c87287f4f44d7a88930285d3f31 Image: harbor.atmosphere.dev/registry.k8s.io/capi-openstack/capi-openstack-controller:v0.12.7 Image ID: harbor.atmosphere.dev/registry.k8s.io/capi-openstack/capi-openstack-controller@sha256:b964c2f374ad4f26a593749d3c737492d5c1821db143b26596c9285b9055a8b4 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 State: Running Started: Wed, 03 Jun 2026 00:43:54 +0000 Last State: Terminated Reason: Error Message: 0.31.14/tools/cache/reflector.go:243 I0603 00:38:27.010086 1 controller.go:217] "Starting workers" controller="openstackcluster" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackCluster" worker count=10 I0603 00:38:27.011267 1 controller.go:217] "Starting workers" controller="openstackmachine" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackMachine" worker count=10 I0603 00:38:27.016557 1 controller.go:217] "Starting workers" controller="openstackfloatingippool" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackFloatingIPPool" worker count=1 I0603 00:38:27.016624 1 controller.go:217] "Starting workers" controller="openstackserver" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackServer" worker count=10 E0603 00:42:49.466736 1 leaderelection.go:429] Failed to update lock optimitically: 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 E0603 00:42:54.467567 1 leaderelection.go:436] 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) I0603 00:42:54.467988 1 leaderelection.go:297] failed to renew lease capo-system/controller-leader-election-capo: timed out waiting for the condition E0603 00:42:59.469441 1 leaderelection.go:322] Failed to release lock: 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) E0603 00:42:59.469578 1 main.go:281] "problem running manager" err="leader election lost" logger="setup" Exit Code: 1 Started: Wed, 03 Jun 2026 00:38:15 +0000 Finished: Wed, 03 Jun 2026 00:42:59 +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-r2gfw (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-r2gfw: 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 36m default-scheduler Successfully assigned capo-system/capo-controller-manager-65565fdb7f-sng5l to instance Warning Unhealthy 31m (x3 over 31m) kubelet Liveness probe failed: Get "http://10.0.0.88:9440/healthz": dial tcp 10.0.0.88:9440: connect: connection refused Normal Killing 31m kubelet Container manager failed liveness probe, will be restarted Normal Pulled 30m (x2 over 36m) kubelet Container image "harbor.atmosphere.dev/registry.k8s.io/capi-openstack/capi-openstack-controller:v0.12.7" already present on machine Normal Created 30m (x2 over 36m) kubelet Created container manager Normal Started 30m (x2 over 36m) kubelet Started container manager Warning Unhealthy 30m (x7 over 31m) kubelet Readiness probe failed: Get "http://10.0.0.88:9440/readyz": dial tcp 10.0.0.88:9440: connect: connection refused