Name: capo-controller-manager-6975759b4b-sdrkt Namespace: capo-system Priority: 0 Service Account: capo-manager Node: instance/199.204.45.69 Start Time: Thu, 09 Apr 2026 16:49:36 +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.159 IPs: IP: 10.0.0.159 Controlled By: ReplicaSet/capo-controller-manager-6975759b4b Containers: manager: Container ID: containerd://2d8de17fd5c8a1ba92e271495fd5403008ce1aabe52016b1fa47a7937bf26390 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, 09 Apr 2026 16:57:36 +0000 Last State: Terminated Reason: Error Message: er" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackServer" worker count=10 I0409 16:56:06.970787 1 controller.go:217] "Starting workers" controller="openstackfloatingippool" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackFloatingIPPool" worker count=1 I0409 16:56:06.970829 1 controller.go:217] "Starting workers" controller="openstackmachine" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackMachine" worker count=10 E0409 16:56:52.163447 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 E0409 16:56:57.157941 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 I0409 16:56:57.157995 1 leaderelection.go:297] failed to renew lease capo-system/controller-leader-election-capo: timed out waiting for the condition E0409 16:56:59.752963 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 E0409 16:56:59.753110 1 main.go:281] "problem running manager" err="leader election lost" logger="setup" I0409 16:56:59.753104 1 recorder.go:104] "capo-controller-manager-6975759b4b-sdrkt_2dc8f4ac-8751-4965-9b65-f341e451caa0 stopped leading" logger="events" type="Normal" object={"kind":"Lease","namespace":"capo-system","name":"controller-leader-election-capo","uid":"cb510434-1b1e-43ad-9a89-c0642ea3012a","apiVersion":"coordination.k8s.io/v1","resourceVersion":"27252"} reason="LeaderElection" Exit Code: 1 Started: Thu, 09 Apr 2026 16:55:33 +0000 Finished: Thu, 09 Apr 2026 16:57:35 +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-2sfrb (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-2sfrb: 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 36m default-scheduler Successfully assigned capo-system/capo-controller-manager-6975759b4b-sdrkt to instance Warning Unhealthy 32m (x3 over 32m) kubelet Liveness probe failed: Get "http://10.0.0.159:9440/healthz": dial tcp 10.0.0.159:9440: connect: connection refused Normal Killing 32m kubelet Container manager failed liveness probe, will be restarted Normal Pulled 30m (x2 over 36m) kubelet Container image "harbor.atmosphere.dev/registry.k8s.io/capi-openstack/capi-openstack-controller:v0.12.4" already present on machine Warning Unhealthy 30m (x12 over 32m) kubelet Readiness probe failed: Get "http://10.0.0.159:9440/readyz": dial tcp 10.0.0.159:9440: connect: connection refused Normal Created 30m (x2 over 36m) kubelet Created container manager Normal Started 30m (x2 over 36m) kubelet Started container manager Warning Unhealthy 28m (x2 over 29m) kubelet Readiness probe failed: Get "http://10.0.0.159:9440/readyz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Warning Unhealthy 28m (x2 over 29m) kubelet Liveness probe failed: Get "http://10.0.0.159:9440/healthz": context deadline exceeded (Client.Timeout exceeded while awaiting headers)