Name: capi-controller-manager-5647546676-hwjjq Namespace: capi-system Priority: 0 Service Account: capi-manager Node: instance/199.204.45.95 Start Time: Sat, 25 Jul 2026 05:19:14 +0000 Labels: cluster.x-k8s.io/provider=cluster-api control-plane=controller-manager pod-template-hash=5647546676 Annotations: Status: Running SeccompProfile: RuntimeDefault IP: 10.0.0.16 IPs: IP: 10.0.0.16 Controlled By: ReplicaSet/capi-controller-manager-5647546676 Containers: manager: Container ID: containerd://186c13d207945b4d20d9fd4275adc0784dbaa8e1a4715f763823fc9228a0563d Image: harbor.atmosphere.dev/registry.k8s.io/cluster-api/cluster-api-controller:v1.13.2 Image ID: harbor.atmosphere.dev/registry.k8s.io/cluster-api/cluster-api-controller@sha256:e53df33f43352d5e7bf5a72fd4171c1447ef2123a4c551484e45395f3dbb1875 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,ClusterTopology=true,RuntimeSDK=false,MachineSetPreflightChecks=true,MachineWaitForVolumeDetachConsiderVolumeAttachments=true,PriorityQueue=true,ReconcilerRateLimiting=true,InPlaceUpdates=false,MachineTaintPropagation=false State: Running Started: Sat, 25 Jul 2026 05:23:35 +0000 Last State: Terminated Reason: Error Message: 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-capi)" lock="capi-system/controller-leader-election-capi" E0725 05:23:28.309227 1 leaderelection.go:452] "Error retrieving lease lock" err="Get \"https://10.96.0.1:443/apis/coordination.k8s.io/v1/namespaces/capi-system/leases/controller-leader-election-capi?timeout=5s\": context deadline exceeded" lock="capi-system/controller-leader-election-capi" I0725 05:23:28.309287 1 leaderelection.go:299] "Failed to renew lease" lock="capi-system/controller-leader-election-capi" err="context deadline exceeded" I0725 05:23:28.309594 1 recorder.go:116] "capi-controller-manager-5647546676-hwjjq_155d22dc-8dfb-43fc-8949-c4f9ccf0deb9 stopped leading" logger="events" type="Normal" object={"kind":"Lease","namespace":"capi-system","name":"controller-leader-election-capi","uid":"61c1583a-4680-4103-bffe-1fff1a4166e2","apiVersion":"coordination.k8s.io/v1","resourceVersion":"26546"} reason="LeaderElection" I0725 05:23:28.309936 1 internal.go:571] "Stopping and waiting for non leader election runnables" I0725 05:23:28.309974 1 internal.go:575] "Stopping and waiting for leader election runnables" I0725 05:23:28.310038 1 internal.go:583] "Stopping and waiting for caches" I0725 05:23:28.310081 1 internal.go:587] "Stopping and waiting for webhooks" I0725 05:23:28.310104 1 internal.go:590] "Stopping and waiting for HTTP servers" I0725 05:23:28.310118 1 internal.go:594] "Wait completed, proceeding to shutdown the manager" I0725 05:23:28.310148 1 internal.go:566] "Stopping and waiting for warmup runnables" E0725 05:23:28.309466 1 main.go:402] "Problem running manager" err="leader election lost" logger="setup" I0725 05:23:28.310489 1 controller.go:326] "Shutdown signal received, waiting for all workers to finish" controller="crdmigrator" controllerGroup="apiextensions.k8s.io" controllerKind="CustomResourceDefinition" Exit Code: 1 Started: Sat, 25 Jul 2026 05:19:15 +0000 Finished: Sat, 25 Jul 2026 05:23:28 +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: POD_NAMESPACE: capi-system (v1:metadata.namespace) POD_NAME: capi-controller-manager-5647546676-hwjjq (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-npvnz (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-npvnz: 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 37m default-scheduler Successfully assigned capi-system/capi-controller-manager-5647546676-hwjjq to instance Warning Unhealthy 33m kubelet Liveness probe failed: Get "http://10.0.0.16:9440/healthz": dial tcp 10.0.0.16:9440: connect: connection refused Warning Unhealthy 33m kubelet Readiness probe failed: Get "http://10.0.0.16:9440/readyz": dial tcp 10.0.0.16:9440: connect: connection refused Normal Pulled 33m (x2 over 37m) kubelet Container image "harbor.atmosphere.dev/registry.k8s.io/cluster-api/cluster-api-controller:v1.13.2" already present on machine Normal Created 33m (x2 over 37m) kubelet Created container manager Normal Started 33m (x2 over 37m) kubelet Started container manager