Name: capi-controller-manager-bc4cf8c95-wwwwm Namespace: capi-system Priority: 0 Service Account: capi-manager Node: instance/199.204.45.30 Start Time: Fri, 29 May 2026 22:40:33 +0000 Labels: cluster.x-k8s.io/provider=cluster-api control-plane=controller-manager pod-template-hash=bc4cf8c95 Annotations: Status: Running SeccompProfile: RuntimeDefault IP: 10.0.0.114 IPs: IP: 10.0.0.114 Controlled By: ReplicaSet/capi-controller-manager-bc4cf8c95 Containers: manager: Container ID: containerd://44a56537833f5082f945d59ecdb87afa30c9a9c3d249008641b1e15dccf6928f Image: harbor.atmosphere.dev/registry.k8s.io/cluster-api/cluster-api-controller:v1.10.5 Image ID: harbor.atmosphere.dev/registry.k8s.io/cluster-api/cluster-api-controller@sha256:d93407d031296336ccbabc8494005672dc048c4ebc616ccfc18f813d49bd87fc Ports: 9443/TCP, 9440/TCP, 8443/TCP Host Ports: 0/TCP, 0/TCP, 0/TCP Command: /manager Args: --leader-elect --diagnostics-address=:8443 --insecure-diagnostics=false --feature-gates=MachinePool=true,ClusterResourceSet=true,ClusterTopology=true,RuntimeSDK=false,MachineSetPreflightChecks=true,MachineWaitForVolumeDetachConsiderVolumeAttachments=true,PriorityQueue=false State: Running Started: Fri, 29 May 2026 22:51:27 +0000 Last State: Terminated Reason: Error Message: ion runnables" I0529 22:51:06.565512 1 internal.go:542] "Stopping and waiting for leader election runnables" I0529 22:51:06.565562 1 internal.go:550] "Stopping and waiting for caches" I0529 22:51:06.565588 1 internal.go:554] "Stopping and waiting for webhooks" I0529 22:51:06.565606 1 internal.go:557] "Stopping and waiting for HTTP servers" I0529 22:51:06.565623 1 internal.go:561] "Wait completed, proceeding to shutdown the manager" I0529 22:51:06.565638 1 controller.go:268] "Shutdown signal received, waiting for all workers to finish" controller="clusterresourceset" controllerGroup="addons.cluster.x-k8s.io" controllerKind="ClusterResourceSet" I0529 22:51:06.565663 1 controller.go:268] "Shutdown signal received, waiting for all workers to finish" controller="machinehealthcheck" controllerGroup="cluster.x-k8s.io" controllerKind="MachineHealthCheck" I0529 22:51:06.565673 1 controller.go:268] "Shutdown signal received, waiting for all workers to finish" controller="clusterresourcesetbinding" controllerGroup="addons.cluster.x-k8s.io" controllerKind="ClusterResourceSetBinding" I0529 22:51:06.565683 1 controller.go:268] "Shutdown signal received, waiting for all workers to finish" controller="machinepool" controllerGroup="cluster.x-k8s.io" controllerKind="MachinePool" E0529 22:51:06.565671 1 main.go:433] "Problem running manager" err="leader election lost" logger="setup" I0529 22:51:06.565711 1 controller.go:268] "Shutdown signal received, waiting for all workers to finish" controller="cluster" controllerGroup="cluster.x-k8s.io" controllerKind="Cluster" I0529 22:51:06.565701 1 controller.go:268] "Shutdown signal received, waiting for all workers to finish" controller="topology/machineset" controllerGroup="cluster.x-k8s.io" controllerKind="MachineSet" I0529 22:51:06.565726 1 controller.go:268] "Shutdown signal received, waiting for all workers to finish" controller="clusterclass" controllerGroup="cluster.x-k8s.io" controllerKind="ClusterClass" Exit Code: 1 Started: Fri, 29 May 2026 22:50:29 +0000 Finished: Fri, 29 May 2026 22:51:06 +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: POD_NAMESPACE: capi-system (v1:metadata.namespace) POD_NAME: capi-controller-manager-bc4cf8c95-wwwwm (v1:metadata.name) POD_UID: (v1:metadata.uid) Mounts: /tmp/k8s-webhook-server/serving-certs from cert (ro) /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-wxdqx (ro) Conditions: Type Status Initialized True Ready True ContainersReady True PodScheduled True Volumes: cert: Type: Secret (a volume populated by a Secret) SecretName: capi-webhook-service-cert Optional: false kube-api-access-wxdqx: 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 31m default-scheduler Successfully assigned capi-system/capi-controller-manager-bc4cf8c95-wwwwm to instance Warning Unhealthy 21m kubelet Readiness probe failed: Get "http://10.0.0.114:9440/readyz": dial tcp 10.0.0.114:9440: connect: connection refused Warning Unhealthy 21m kubelet Liveness probe failed: Get "http://10.0.0.114:9440/healthz": dial tcp 10.0.0.114:9440: connect: connection refused Warning BackOff 20m (x2 over 20m) kubelet Back-off restarting failed container manager in pod capi-controller-manager-bc4cf8c95-wwwwm_capi-system(0937c203-972a-4564-a2ee-f08668397a15) Normal Pulled 20m (x3 over 31m) kubelet Container image "harbor.atmosphere.dev/registry.k8s.io/cluster-api/cluster-api-controller:v1.10.5" already present on machine Normal Created 20m (x3 over 31m) kubelet Created container manager Normal Started 20m (x3 over 31m) kubelet Started container manager