Name: capo-controller-manager-65565fdb7f-d2rxm Namespace: capo-system Priority: 0 Service Account: capo-manager Node: instance/199.204.45.3 Start Time: Sat, 25 Apr 2026 01:03:52 +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.80 IPs: IP: 10.0.0.80 Controlled By: ReplicaSet/capo-controller-manager-65565fdb7f Containers: manager: Container ID: containerd://bff4b73f2f1c833b48459fc0edf61c490c67feb27750e207bafd29fb558ade0d 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: Sat, 25 Apr 2026 01:11:31 +0000 Last State: Terminated Reason: Error Message: 1] "Wait completed, proceeding to shutdown the manager" I0425 01:10:45.957515 1 controller.go:237] "Shutdown signal received, waiting for all workers to finish" controller="openstackcluster" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackCluster" I0425 01:10:45.957533 1 controller.go:237] "Shutdown signal received, waiting for all workers to finish" controller="openstackserver" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackServer" I0425 01:10:45.957323 1 recorder.go:104] "capo-controller-manager-65565fdb7f-d2rxm_634ba274-bdd0-4ad7-9ea0-00c0533d4911 stopped leading" logger="events" type="Normal" object={"kind":"Lease","namespace":"capo-system","name":"controller-leader-election-capo","uid":"ab6f00b3-023a-48dd-842d-7eb8f27cff33","apiVersion":"coordination.k8s.io/v1","resourceVersion":"18127"} reason="LeaderElection" I0425 01:10:45.957559 1 controller.go:237] "Shutdown signal received, waiting for all workers to finish" controller="openstackmachine" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackMachine" I0425 01:10:45.957588 1 controller.go:237] "Shutdown signal received, waiting for all workers to finish" controller="openstackfloatingippool" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackFloatingIPPool" I0425 01:10:45.957702 1 controller.go:239] "All workers finished" controller="openstackcluster" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackCluster" I0425 01:10:45.957732 1 controller.go:239] "All workers finished" controller="openstackmachine" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackMachine" I0425 01:10:45.957825 1 controller.go:239] "All workers finished" controller="openstackfloatingippool" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackFloatingIPPool" E0425 01:10:45.958779 1 main.go:281] "problem running manager" err="leader election lost" logger="setup" Exit Code: 1 Started: Sat, 25 Apr 2026 01:09:29 +0000 Finished: Sat, 25 Apr 2026 01:10:45 +0000 Ready: True Restart Count: 3 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-prwf4 (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-prwf4: 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 28m default-scheduler Successfully assigned capo-system/capo-controller-manager-65565fdb7f-d2rxm to instance Normal Killing 24m kubelet Container manager failed liveness probe, will be restarted Warning Unhealthy 23m kubelet Readiness probe failed: Get "http://10.0.0.80:9440/readyz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Warning Unhealthy 23m kubelet Liveness probe failed: Get "http://10.0.0.80:9440/healthz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Normal Pulled 23m (x3 over 28m) kubelet Container image "harbor.atmosphere.dev/registry.k8s.io/capi-openstack/capi-openstack-controller:v0.12.7" already present on machine Normal Created 23m (x3 over 28m) kubelet Created container manager Normal Started 23m (x3 over 28m) kubelet Started container manager Warning Unhealthy 21m (x6 over 25m) kubelet Liveness probe failed: Get "http://10.0.0.80:9440/healthz": dial tcp 10.0.0.80:9440: connect: connection refused Warning Unhealthy 21m (x8 over 25m) kubelet Readiness probe failed: Get "http://10.0.0.80:9440/readyz": dial tcp 10.0.0.80:9440: connect: connection refused