Name: capo-controller-manager-65565fdb7f-8k2nh Namespace: capo-system Priority: 0 Service Account: capo-manager Node: instance/199.204.45.77 Start Time: Sun, 10 May 2026 04:52:20 +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.18 IPs: IP: 10.0.0.18 Controlled By: ReplicaSet/capo-controller-manager-65565fdb7f Containers: manager: Container ID: containerd://00cff5374c6d56cbeeaf64ffd8396043ff917c5a22eb9e9cd88d04f53c026caf 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: Sun, 10 May 2026 04:57:19 +0000 Last State: Terminated Reason: Error Message: openstackcluster" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackCluster" worker count=10 I0510 04:56:30.164266 1 controller.go:217] "Starting workers" controller="openstackmachine" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackMachine" worker count=10 I0510 04:56:30.168777 1 controller.go:217] "Starting workers" controller="openstackserver" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackServer" worker count=10 E0510 04:56:50.900029 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": context deadline exceeded, falling back to slow path E0510 04:56:55.901501 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": net/http: request canceled (Client.Timeout exceeded while awaiting headers) I0510 04:56:55.901579 1 leaderelection.go:297] failed to renew lease capo-system/controller-leader-election-capo: timed out waiting for the condition E0510 04:56:58.984149 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 I0510 04:56:58.984369 1 recorder.go:104] "capo-controller-manager-65565fdb7f-8k2nh_48ec55d8-fd10-4da2-ba84-9cc7dd37db17 stopped leading" logger="events" type="Normal" object={"kind":"Lease","namespace":"capo-system","name":"controller-leader-election-capo","uid":"eded4e15-873f-4848-82ef-0a602debe4bb","apiVersion":"coordination.k8s.io/v1","resourceVersion":"29037"} reason="LeaderElection" E0510 04:56:58.984767 1 main.go:281] "problem running manager" err="leader election lost" logger="setup" Exit Code: 1 Started: Sun, 10 May 2026 04:56:04 +0000 Finished: Sun, 10 May 2026 04:57:16 +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-8tzzz (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-8tzzz: 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 33m default-scheduler Successfully assigned capo-system/capo-controller-manager-65565fdb7f-8k2nh to instance Warning Unhealthy 30m (x3 over 30m) kubelet Liveness probe failed: Get "http://10.0.0.18:9440/healthz": dial tcp 10.0.0.18:9440: connect: connection refused Normal Killing 30m kubelet Container manager failed liveness probe, will be restarted Warning Unhealthy 30m (x6 over 30m) kubelet Readiness probe failed: Get "http://10.0.0.18:9440/readyz": dial tcp 10.0.0.18:9440: connect: connection refused Warning Unhealthy 29m (x2 over 29m) kubelet Liveness probe failed: Get "http://10.0.0.18: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.18:9440/readyz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Normal Pulled 29m (x3 over 33m) kubelet Container image "harbor.atmosphere.dev/registry.k8s.io/capi-openstack/capi-openstack-controller:v0.12.7" already present on machine Normal Created 29m (x3 over 33m) kubelet Created container manager Normal Started 28m (x3 over 33m) kubelet Started container manager