Name: capo-controller-manager-56cf844ccd-bdjjs Namespace: capo-system Priority: 0 Service Account: capo-manager Node: instance/199.19.213.162 Start Time: Thu, 23 Jul 2026 11:27:22 +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.2 IPs: IP: 10.0.0.2 Controlled By: ReplicaSet/capo-controller-manager-56cf844ccd Containers: manager: Container ID: containerd://64b82eb231e4c8627ed0207263b2c09a5fe0a1e9df5b55dad1d6391b5a36bd3f 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: Thu, 23 Jul 2026 11:47:03 +0000 Last State: Terminated Reason: Error Message: ontrollerKind="OpenStackCluster" worker count=10 I0723 11:43:04.253262 1 controller.go:286] "Starting Controller" controller="openstackfloatingippool" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackFloatingIPPool" I0723 11:43:04.253289 1 controller.go:289] "Starting workers" controller="openstackfloatingippool" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackFloatingIPPool" worker count=1 I0723 11:43:04.254707 1 controller.go:286] "Starting Controller" controller="openstackserver" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackServer" I0723 11:43:04.254738 1 controller.go:289] "Starting workers" controller="openstackserver" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackServer" worker count=10 E0723 11:45:49.325262 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 E0723 11:45:54.323267 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 I0723 11:45:54.323312 1 leaderelection.go:297] failed to renew lease capo-system/controller-leader-election-capo: context deadline exceeded I0723 11:46:00.744587 1 recorder.go:104] "capo-controller-manager-56cf844ccd-bdjjs_761847e6-96b4-4dd8-9e91-3fa6ae5eebd4 stopped leading" logger="events" type="Normal" object={"kind":"Lease","namespace":"capo-system","name":"controller-leader-election-capo","uid":"c933bdc9-4580-4702-b3bb-d48777b75a9c","apiVersion":"coordination.k8s.io/v1","resourceVersion":"32303"} reason="LeaderElection" E0723 11:46:00.745110 1 main.go:304] "problem running manager" err="leader election lost" logger="setup" Exit Code: 1 Started: Thu, 23 Jul 2026 11:42:46 +0000 Finished: Thu, 23 Jul 2026 11:46:00 +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-trlql (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-trlql: 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-56cf844ccd-bdjjs to instance Normal Pulled 37m (x2 over 42m) kubelet Container image "harbor.atmosphere.dev/registry.k8s.io/capi-openstack/capi-openstack-controller:v0.14.4" already present on machine Normal Killing 37m (x3 over 38m) kubelet Container manager failed liveness probe, will be restarted Normal Created 37m (x2 over 42m) kubelet Created container manager Normal Started 37m (x2 over 42m) kubelet Started container manager Warning Unhealthy 27m (x7 over 38m) kubelet Liveness probe failed: Get "http://10.0.0.2:9440/healthz": dial tcp 10.0.0.2:9440: connect: connection refused Warning Unhealthy 27m (x26 over 38m) kubelet Readiness probe failed: Get "http://10.0.0.2:9440/readyz": dial tcp 10.0.0.2:9440: connect: connection refused