Name: capo-controller-manager-56cf844ccd-skcrp Namespace: capo-system Priority: 0 Service Account: capo-manager Node: instance/199.204.45.156 Start Time: Mon, 27 Jul 2026 22:32:51 +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.197 IPs: IP: 10.0.0.197 Controlled By: ReplicaSet/capo-controller-manager-56cf844ccd Containers: manager: Container ID: containerd://89267422e589d8394e7f530d1d39e8d5f832a0f153d0b83ba2f77939f244dc47 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: Mon, 27 Jul 2026 22:37:59 +0000 Last State: Terminated Reason: Error Message: 27 22:32:55.665751 1 controller.go:286] "Starting Controller" controller="openstackserver" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackServer" I0727 22:32:55.665787 1 controller.go:289] "Starting workers" controller="openstackserver" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackServer" worker count=10 I0727 22:32:55.667909 1 controller.go:286] "Starting Controller" controller="openstackfloatingippool" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackFloatingIPPool" I0727 22:32:55.667934 1 controller.go:289] "Starting workers" controller="openstackfloatingippool" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackFloatingIPPool" worker count=1 E0727 22:36:42.242678 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 E0727 22:36:47.241985 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 I0727 22:36:47.242055 1 leaderelection.go:297] failed to renew lease capo-system/controller-leader-election-capo: context deadline exceeded E0727 22:36:55.087719 1 main.go:304] "problem running manager" err="leader election lost" logger="setup" I0727 22:36:55.087712 1 recorder.go:104] "capo-controller-manager-56cf844ccd-skcrp_8130c5f9-f557-48cc-b6e8-fc310417a7e0 stopped leading" logger="events" type="Normal" object={"kind":"Lease","namespace":"capo-system","name":"controller-leader-election-capo","uid":"de60311a-7132-4bf6-ab17-93ca4932b5a9","apiVersion":"coordination.k8s.io/v1","resourceVersion":"26098"} reason="LeaderElection" Exit Code: 1 Started: Mon, 27 Jul 2026 22:32:51 +0000 Finished: Mon, 27 Jul 2026 22:37:55 +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-bbth2 (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-bbth2: 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 43m default-scheduler Successfully assigned capo-system/capo-controller-manager-56cf844ccd-skcrp to instance Warning Unhealthy 38m (x3 over 39m) kubelet Liveness probe failed: Get "http://10.0.0.197:9440/healthz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Normal Killing 38m kubelet Container manager failed liveness probe, will be restarted Warning Unhealthy 38m (x7 over 39m) kubelet Readiness probe failed: Get "http://10.0.0.197:9440/readyz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Normal Pulled 38m (x2 over 43m) kubelet Container image "harbor.atmosphere.dev/registry.k8s.io/capi-openstack/capi-openstack-controller:v0.14.4" already present on machine Normal Created 38m (x2 over 43m) kubelet Created container manager Normal Started 38m (x2 over 43m) kubelet Started container manager