Name: capo-controller-manager-6975759b4b-npvcf Namespace: capo-system Priority: 0 Service Account: capo-manager Node: instance/162.253.55.140 Start Time: Thu, 05 Mar 2026 17:21:57 +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.55 IPs: IP: 10.0.0.55 Controlled By: ReplicaSet/capo-controller-manager-6975759b4b Containers: manager: Container ID: containerd://9ad089863c4deec3a9704b6d72995114cd6ad15c3351440ded75a4024c1b9235 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: Thu, 05 Mar 2026 17:26:49 +0000 Last State: Terminated Reason: Error Message: g workers" controller="openstackfloatingippool" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackFloatingIPPool" worker count=1 I0305 17:25:35.307958 1 controller.go:217] "Starting workers" controller="openstackserver" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackServer" worker count=10 I0305 17:25:35.307977 1 controller.go:217] "Starting workers" controller="openstackmachine" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackMachine" worker count=10 E0305 17:26:09.638970 1 leaderelection.go:429] Failed to update lock optimitically: the 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-capo), falling back to slow path E0305 17:26:14.638746 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 I0305 17:26:14.638801 1 leaderelection.go:297] failed to renew lease capo-system/controller-leader-election-capo: timed out waiting for the condition E0305 17:26:15.483535 1 leaderelection.go:322] Failed to release lock: Operation cannot be fulfilled on leases.coordination.k8s.io "controller-leader-election-capo": the object has been modified; please apply your changes to the latest version and try again E0305 17:26:15.483649 1 main.go:281] "problem running manager" err="leader election lost" logger="setup" I0305 17:26:15.483647 1 recorder.go:104] "capo-controller-manager-6975759b4b-npvcf_8ea13d23-eaf8-4aa5-971f-456186054ce1 stopped leading" logger="events" type="Normal" object={"kind":"Lease","namespace":"capo-system","name":"controller-leader-election-capo","uid":"ad51dba1-20e3-47c4-b72a-eb7cca74b1e7","apiVersion":"coordination.k8s.io/v1","resourceVersion":"23793"} reason="LeaderElection" Exit Code: 1 Started: Thu, 05 Mar 2026 17:25:35 +0000 Finished: Thu, 05 Mar 2026 17:26:48 +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-s4lpq (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-s4lpq: 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-npvcf to instance Warning Unhealthy 31m kubelet Liveness probe failed: Get "http://10.0.0.55:9440/healthz": dial tcp 10.0.0.55:9440: connect: connection refused Warning Unhealthy 31m kubelet Readiness probe failed: Get "http://10.0.0.55:9440/readyz": dial tcp 10.0.0.55:9440: connect: connection refused Warning Unhealthy 30m (x3 over 30m) kubelet Liveness probe failed: Get "http://10.0.0.55:9440/healthz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Normal Killing 30m kubelet Container manager failed liveness probe, will be restarted Warning Unhealthy 30m (x4 over 30m) kubelet Readiness probe failed: Get "http://10.0.0.55:9440/readyz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Normal Pulled 29m (x3 over 34m) kubelet Container image "harbor.atmosphere.dev/registry.k8s.io/capi-openstack/capi-openstack-controller:v0.12.4" already present on machine Warning Unhealthy 29m kubelet Readiness probe failed: Get "http://10.0.0.55:9440/readyz": read tcp 10.0.0.183:46646->10.0.0.55:9440: read: connection reset by peer Normal Created 29m (x3 over 34m) kubelet Created container manager Normal Started 29m (x3 over 34m) kubelet Started container manager Warning Unhealthy 29m kubelet Readiness probe failed: HTTP probe failed with statuscode: 500