Name: capo-controller-manager-56cf844ccd-992lm Namespace: capo-system Priority: 0 Service Account: capo-manager Node: instance/199.204.45.138 Start Time: Tue, 30 Jun 2026 19:09:16 +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.7 IPs: IP: 10.0.0.7 Controlled By: ReplicaSet/capo-controller-manager-56cf844ccd Containers: manager: Container ID: containerd://043513078b2829dcef08f14eb9f0409cd17d7478c560b19f8df0ae7fa9a0eea1 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: Tue, 30 Jun 2026 19:14:45 +0000 Last State: Terminated Reason: Error Message: ol" I0630 19:09:20.674763 1 controller.go:289] "Starting workers" controller="openstackfloatingippool" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackFloatingIPPool" worker count=1 E0630 19:12:57.693170 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": context deadline exceeded, falling back to slow path E0630 19:13:02.703647 1 leaderelection.go:448] 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 I0630 19:13:02.703695 1 leaderelection.go:297] failed to renew lease capo-system/controller-leader-election-capo: context deadline exceeded E0630 19:13:07.704498 1 leaderelection.go:316] 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) E0630 19:13:07.704670 1 main.go:304] "problem running manager" err="leader election lost" logger="setup" I0630 19:13:07.704668 1 recorder.go:104] "capo-controller-manager-56cf844ccd-992lm_732bb810-73e6-4bcf-a1f1-f60e6fa997d0 stopped leading" logger="events" type="Normal" object={"kind":"Lease","namespace":"capo-system","name":"controller-leader-election-capo","uid":"1cf1710f-a585-4917-a0e5-d3aef57c9f29","apiVersion":"coordination.k8s.io/v1","resourceVersion":"27848"} reason="LeaderElection" I0630 19:13:07.704724 1 internal.go:555] "Stopping and waiting for non leader election runnables" I0630 19:13:07.704740 1 internal.go:559] "Stopping and waiting for leader election runnables" I0630 19:13:07.704769 1 internal.go:567] "Stopping and waiting for caches" Exit Code: 1 Started: Tue, 30 Jun 2026 19:09:17 +0000 Finished: Tue, 30 Jun 2026 19:13:07 +0000 Ready: True Restart Count: 1 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-r5jg6 (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-r5jg6: 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 39m default-scheduler Successfully assigned capo-system/capo-controller-manager-56cf844ccd-992lm to instance Normal Created 39m kubelet Created container manager Normal Started 39m kubelet Started container manager Warning Unhealthy 35m (x3 over 35m) kubelet Liveness probe failed: Get "http://10.0.0.7:9440/healthz": dial tcp 10.0.0.7:9440: connect: connection refused Normal Pulled 34m (x2 over 39m) kubelet Container image "harbor.atmosphere.dev/registry.k8s.io/capi-openstack/capi-openstack-controller:v0.14.4" already present on machine Warning Unhealthy 34m (x14 over 35m) kubelet Readiness probe failed: Get "http://10.0.0.7:9440/readyz": dial tcp 10.0.0.7:9440: connect: connection refused Normal Killing 34m (x5 over 35m) kubelet Container manager failed liveness probe, will be restarted