Name: capo-controller-manager-6975759b4b-pvzxp Namespace: capo-system Priority: 0 Service Account: capo-manager Node: instance/199.19.213.111 Start Time: Mon, 13 Apr 2026 15:05:24 +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.61 IPs: IP: 10.0.0.61 Controlled By: ReplicaSet/capo-controller-manager-6975759b4b Containers: manager: Container ID: containerd://ad95d711a9a41d696b4128cafb11f717cc5c15812c81c421b056fbb820005920 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: Mon, 13 Apr 2026 15:10:12 +0000 Last State: Terminated Reason: Error Message: ="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackMachine" worker count=10 I0413 15:05:36.920262 1 controller.go:217] "Starting workers" controller="openstackserver" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackServer" worker count=10 I0413 15:05:36.920417 1 controller.go:217] "Starting workers" controller="openstackcluster" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackCluster" worker count=10 E0413 15:09:29.164927 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 E0413 15:09:34.167474 1 leaderelection.go:436] error retrieving resource lock capo-system/controller-leader-election-capo: the server was unable to return a response in the time allotted, but may still be processing the request (get leases.coordination.k8s.io controller-leader-election-capo) I0413 15:09:34.167521 1 leaderelection.go:297] failed to renew lease capo-system/controller-leader-election-capo: timed out waiting for the condition E0413 15:09:39.168437 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) E0413 15:09:39.168535 1 main.go:281] "problem running manager" err="leader election lost" logger="setup" I0413 15:09:39.168557 1 recorder.go:104] "capo-controller-manager-6975759b4b-pvzxp_b05472f6-d17c-4965-ad36-2cb04e1a5d01 stopped leading" logger="events" type="Normal" object={"kind":"Lease","namespace":"capo-system","name":"controller-leader-election-capo","uid":"a2a01814-489e-41fa-ade3-4ff671193f05","apiVersion":"coordination.k8s.io/v1","resourceVersion":"25493"} reason="LeaderElection" Exit Code: 1 Started: Mon, 13 Apr 2026 15:05:25 +0000 Finished: Mon, 13 Apr 2026 15:09: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-87ght (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-87ght: 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 34m default-scheduler Successfully assigned capo-system/capo-controller-manager-6975759b4b-pvzxp to instance Warning Unhealthy 29m (x2 over 29m) kubelet Liveness probe failed: Get "http://10.0.0.61:9440/healthz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Warning Unhealthy 29m (x2 over 29m) kubelet Readiness probe failed: Get "http://10.0.0.61:9440/readyz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Warning Unhealthy 29m kubelet Liveness probe failed: Get "http://10.0.0.61:9440/healthz": dial tcp 10.0.0.61:9440: connect: connection refused Warning Unhealthy 29m kubelet Readiness probe failed: Get "http://10.0.0.61:9440/readyz": dial tcp 10.0.0.61:9440: connect: connection refused Normal Killing 29m kubelet Container manager failed liveness probe, will be restarted Normal Pulled 29m (x2 over 34m) kubelet Container image "harbor.atmosphere.dev/registry.k8s.io/capi-openstack/capi-openstack-controller:v0.12.4" already present on machine Normal Created 29m (x2 over 34m) kubelet Created container manager Normal Started 29m (x2 over 34m) kubelet Started container manager