Name: capo-controller-manager-56cf844ccd-n6hz2 Namespace: capo-system Priority: 0 Service Account: capo-manager Node: instance/199.204.45.95 Start Time: Wed, 01 Jul 2026 08:16:57 +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.38 IPs: IP: 10.0.0.38 Controlled By: ReplicaSet/capo-controller-manager-56cf844ccd Containers: manager: Container ID: containerd://f9cb5712f6e8fbbd963dd81358ece8be54512b7ebac9b9cc26cb16af2fac76e6 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, 01 Jul 2026 08:22:52 +0000 Last State: Terminated Reason: Error Message: structure.cluster.x-k8s.io" controllerKind="OpenStackFloatingIPPool" I0701 08:17:10.156639 1 controller.go:289] "Starting workers" controller="openstackfloatingippool" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackFloatingIPPool" worker count=1 E0701 08:21:36.808549 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 (Client.Timeout exceeded while awaiting headers), falling back to slow path E0701 08:21:55.141804 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 E0701 08:22:00.141752 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 I0701 08:22:00.141835 1 leaderelection.go:297] failed to renew lease capo-system/controller-leader-election-capo: context deadline exceeded E0701 08:22:05.142961 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": context deadline exceeded E0701 08:22:05.143451 1 main.go:304] "problem running manager" err="leader election lost" logger="setup" I0701 08:22:05.143964 1 recorder.go:104] "capo-controller-manager-56cf844ccd-n6hz2_0ed3df0a-bd15-4e43-b0b5-0149c3c0b75f stopped leading" logger="events" type="Normal" object={"kind":"Lease","namespace":"capo-system","name":"controller-leader-election-capo","uid":"f068975a-cb96-4770-898b-71086cd8b417","apiVersion":"coordination.k8s.io/v1","resourceVersion":"26479"} reason="LeaderElection" Exit Code: 1 Started: Wed, 01 Jul 2026 08:16:58 +0000 Finished: Wed, 01 Jul 2026 08:22:52 +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-l4t8t (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-l4t8t: 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 35m default-scheduler Successfully assigned capo-system/capo-controller-manager-56cf844ccd-n6hz2 to instance Warning Unhealthy 30m (x3 over 30m) kubelet Liveness probe failed: Get "http://10.0.0.38:9440/healthz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) 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.38:9440/readyz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Normal Pulled 29m (x2 over 35m) kubelet Container image "harbor.atmosphere.dev/registry.k8s.io/capi-openstack/capi-openstack-controller:v0.14.4" already present on machine Normal Created 29m (x2 over 35m) kubelet Created container manager Normal Started 29m (x2 over 35m) kubelet Started container manager