Name: capo-controller-manager-65565fdb7f-8bk2w Namespace: capo-system Priority: 0 Service Account: capo-manager Node: instance/199.19.213.146 Start Time: Fri, 08 May 2026 11:19:22 +0000 Labels: cluster.x-k8s.io/provider=infrastructure-openstack control-plane=capo-controller-manager pod-template-hash=65565fdb7f Annotations: Status: Running SeccompProfile: RuntimeDefault IP: 10.0.0.35 IPs: IP: 10.0.0.35 Controlled By: ReplicaSet/capo-controller-manager-65565fdb7f Containers: manager: Container ID: containerd://e204b343ee98c95764a633050571538e5f2eb367cc028b5fe331bc516bc755e1 Image: harbor.atmosphere.dev/registry.k8s.io/capi-openstack/capi-openstack-controller:v0.12.7 Image ID: harbor.atmosphere.dev/registry.k8s.io/capi-openstack/capi-openstack-controller@sha256:b964c2f374ad4f26a593749d3c737492d5c1821db143b26596c9285b9055a8b4 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: Fri, 08 May 2026 11:48:18 +0000 Last State: Terminated Reason: Error Message: o" controllerKind="OpenStackServer" worker count=10 I0508 11:47:09.642037 1 controller.go:217] "Starting workers" controller="openstackfloatingippool" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackFloatingIPPool" worker count=1 I0508 11:47:09.642080 1 controller.go:217] "Starting workers" controller="openstackmachine" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackMachine" worker count=10 E0508 11:47:20.951068 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 E0508 11:47:25.951244 1 leaderelection.go:472] Failed to update 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 I0508 11:47:25.951309 1 leaderelection.go:297] failed to renew lease capo-system/controller-leader-election-capo: timed out waiting for the condition I0508 11:47:30.696740 1 recorder.go:104] "capo-controller-manager-65565fdb7f-8bk2w_95c3850b-da5e-48ea-ab18-1b471ec4d6f2 stopped leading" logger="events" type="Normal" object={"kind":"Lease","namespace":"capo-system","name":"controller-leader-election-capo","uid":"89cf229e-0868-45f4-81bd-408e956a2299","apiVersion":"coordination.k8s.io/v1","resourceVersion":"35965"} reason="LeaderElection" E0508 11:47:30.696780 1 main.go:281] "problem running manager" err="leader election lost" logger="setup" I0508 11:47:30.696800 1 internal.go:538] "Stopping and waiting for non leader election runnables" I0508 11:47:30.696816 1 internal.go:542] "Stopping and waiting for leader election runnables" I0508 11:47:30.696835 1 internal.go:550] "Stopping and waiting for caches" I0508 11:47:30.696854 1 internal.go:554] "Stopping and waiting for webhooks" Exit Code: 1 Started: Fri, 08 May 2026 11:46:11 +0000 Finished: Fri, 08 May 2026 11:47:30 +0000 Ready: True Restart Count: 4 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-szzts (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-szzts: 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 42m default-scheduler Successfully assigned capo-system/capo-controller-manager-65565fdb7f-8bk2w to instance Normal Killing 38m kubelet Container manager failed liveness probe, will be restarted Normal Started 22m (x3 over 42m) kubelet Started container manager Warning Unhealthy 16m (x6 over 39m) kubelet Liveness probe failed: Get "http://10.0.0.35:9440/healthz": dial tcp 10.0.0.35:9440: connect: connection refused Warning Unhealthy 16m (x12 over 39m) kubelet Readiness probe failed: Get "http://10.0.0.35:9440/readyz": dial tcp 10.0.0.35:9440: connect: connection refused Normal Pulled 16m (x4 over 42m) kubelet Container image "harbor.atmosphere.dev/registry.k8s.io/capi-openstack/capi-openstack-controller:v0.12.7" already present on machine Normal Created 15m (x4 over 42m) kubelet Created container manager