Name: capo-controller-manager-6975759b4b-6klzw Namespace: capo-system Priority: 0 Service Account: capo-manager Node: instance/199.19.213.236 Start Time: Wed, 04 Mar 2026 16:16:05 +0000 Labels: cluster.x-k8s.io/provider=infrastructure-openstack control-plane=capo-controller-manager pod-template-hash=6975759b4b Annotations: Status: Running SeccompProfile: RuntimeDefault IP: 10.0.0.48 IPs: IP: 10.0.0.48 Controlled By: ReplicaSet/capo-controller-manager-6975759b4b Containers: manager: Container ID: containerd://0de5c6d829369a47c665f8369c0b5e7e74268f762fd5acf95bb066b3f270ea53 Image: harbor.atmosphere.dev/registry.k8s.io/capi-openstack/capi-openstack-controller:v0.12.4 Image ID: harbor.atmosphere.dev/registry.k8s.io/capi-openstack/capi-openstack-controller@sha256:237da708e483aa8c39766a217d25e45de52816d446764569c77550e6f56f0970 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, 04 Mar 2026 16:23:30 +0000 Last State: Terminated Reason: Error Message: "Starting workers" controller="openstackcluster" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackCluster" worker count=10 I0304 16:21:15.844771 1 controller.go:217] "Starting workers" controller="openstackserver" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackServer" worker count=10 I0304 16:21:15.844817 1 controller.go:217] "Starting workers" controller="openstackmachine" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackMachine" worker count=10 E0304 16:21:29.605374 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 E0304 16:21:34.605723 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": context deadline exceeded I0304 16:21:34.605788 1 leaderelection.go:297] failed to renew lease capo-system/controller-leader-election-capo: timed out waiting for the condition E0304 16:21:39.607097 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": context deadline exceeded E0304 16:21:39.607273 1 main.go:281] "problem running manager" err="leader election lost" logger="setup" I0304 16:21:39.607309 1 recorder.go:104] "capo-controller-manager-6975759b4b-6klzw_10f4abb3-23f4-43b3-be54-5846b6a6e07e stopped leading" logger="events" type="Normal" object={"kind":"Lease","namespace":"capo-system","name":"controller-leader-election-capo","uid":"a6198eb2-93f8-44d4-97ed-13f69ac8da11","apiVersion":"coordination.k8s.io/v1","resourceVersion":"24700"} reason="LeaderElection" Exit Code: 1 Started: Wed, 04 Mar 2026 16:21:00 +0000 Finished: Wed, 04 Mar 2026 16:22:15 +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: 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-zsdcc (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-zsdcc: 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 41m default-scheduler Successfully assigned capo-system/capo-controller-manager-6975759b4b-6klzw to instance Normal Pulled 37m (x2 over 41m) kubelet Container image "harbor.atmosphere.dev/registry.k8s.io/capi-openstack/capi-openstack-controller:v0.12.4" already present on machine Warning Unhealthy 37m (x3 over 38m) kubelet Liveness probe failed: Get "http://10.0.0.48:9440/healthz": dial tcp 10.0.0.48:9440: connect: connection refused Normal Killing 37m kubelet Container manager failed liveness probe, will be restarted Warning Unhealthy 36m (x10 over 38m) kubelet Readiness probe failed: Get "http://10.0.0.48:9440/readyz": dial tcp 10.0.0.48:9440: connect: connection refused Normal Created 36m (x2 over 41m) kubelet Created container manager Normal Started 36m (x2 over 41m) kubelet Started container manager Warning Unhealthy 35m (x3 over 35m) kubelet Readiness probe failed: Get "http://10.0.0.48:9440/readyz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Warning Unhealthy 35m (x3 over 35m) kubelet Liveness probe failed: Get "http://10.0.0.48:9440/healthz": context deadline exceeded (Client.Timeout exceeded while awaiting headers)