Name: capo-controller-manager-56cf844ccd-s47td Namespace: capo-system Priority: 0 Service Account: capo-manager Node: instance/199.204.45.109 Start Time: Wed, 24 Jun 2026 18:58:20 +0000 Labels: cluster.x-k8s.io/provider=infrastructure-openstack control-plane=capo-controller-manager pod-template-hash=56cf844ccd Annotations: Status: Running SeccompProfile: RuntimeDefault IP: 10.0.0.58 IPs: IP: 10.0.0.58 Controlled By: ReplicaSet/capo-controller-manager-56cf844ccd Containers: manager: Container ID: containerd://981e499ce19fa63c2eef6df8fdd3415aeaf840066acf1a194b0ac86349e930ad Image: harbor.atmosphere.dev/registry.k8s.io/capi-openstack/capi-openstack-controller:v0.14.4 Image ID: harbor.atmosphere.dev/registry.k8s.io/capi-openstack/capi-openstack-controller@sha256:b428de23d97c69ebb350e2359e73eb6ec92572e5dfab8cc4cea9994c01fa4ee0 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 --feature-gates=PriorityQueue=false,AutoScaleFromZero=false State: Running Started: Wed, 24 Jun 2026 19:04:45 +0000 Last State: Terminated Reason: Error Message: ructure.cluster.x-k8s.io" controllerKind="OpenStackCluster" worker count=10 I0624 19:02:53.957964 1 controller.go:286] "Starting Controller" controller="openstackserver" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackServer" I0624 19:02:53.957999 1 controller.go:289] "Starting workers" controller="openstackserver" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackServer" worker count=10 I0624 19:02:53.958020 1 controller.go:286] "Starting Controller" controller="openstackmachine" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackMachine" I0624 19:02:53.958036 1 controller.go:289] "Starting workers" controller="openstackmachine" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackMachine" worker count=10 E0624 19:04:13.594659 1 leaderelection.go:441] Failed to update lock optimistically: 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 E0624 19:04:18.594444 1 leaderelection.go:484] 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 I0624 19:04:18.594514 1 leaderelection.go:297] failed to renew lease capo-system/controller-leader-election-capo: context deadline exceeded E0624 19:04:23.196534 1 main.go:304] "problem running manager" err="leader election lost" logger="setup" I0624 19:04:23.196547 1 recorder.go:104] "capo-controller-manager-56cf844ccd-s47td_a6a682cb-be22-41b5-a95c-011d25adb6bf stopped leading" logger="events" type="Normal" object={"kind":"Lease","namespace":"capo-system","name":"controller-leader-election-capo","uid":"dca7c449-402e-435b-bcde-200df88a786c","apiVersion":"coordination.k8s.io/v1","resourceVersion":"27417"} reason="LeaderElection" Exit Code: 1 Started: Wed, 24 Jun 2026 19:02:33 +0000 Finished: Wed, 24 Jun 2026 19:04:43 +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-rwcs5 (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-rwcs5: 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 47m default-scheduler Successfully assigned capo-system/capo-controller-manager-56cf844ccd-s47td to instance Warning Unhealthy 43m (x3 over 44m) kubelet Liveness probe failed: Get "http://10.0.0.58:9440/healthz": dial tcp 10.0.0.58:9440: connect: connection refused Normal Created 43m (x2 over 47m) kubelet Created container manager Normal Started 43m (x2 over 47m) kubelet Started container manager Warning Unhealthy 43m (x9 over 44m) kubelet Readiness probe failed: Get "http://10.0.0.58:9440/readyz": dial tcp 10.0.0.58:9440: connect: connection refused Normal Killing 43m (x3 over 43m) kubelet Container manager failed liveness probe, will be restarted Warning Unhealthy 41m (x2 over 41m) kubelet Liveness probe failed: Get "http://10.0.0.58:9440/healthz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Warning Unhealthy 41m (x2 over 41m) kubelet Readiness probe failed: Get "http://10.0.0.58:9440/readyz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Normal Pulled 41m (x3 over 47m) kubelet Container image "harbor.atmosphere.dev/registry.k8s.io/capi-openstack/capi-openstack-controller:v0.14.4" already present on machine