Name: capo-controller-manager-56cf844ccd-xqhzg Namespace: capo-system Priority: 0 Service Account: capo-manager Node: instance/199.19.213.68 Start Time: Thu, 09 Jul 2026 17:38:30 +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.192 IPs: IP: 10.0.0.192 Controlled By: ReplicaSet/capo-controller-manager-56cf844ccd Containers: manager: Container ID: containerd://83ddd53c6b1dd9f1291c3334956a4c6ba80c435a443456c51f42a38f30ed85a5 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, 09 Jul 2026 17:45:17 +0000 Last State: Terminated Reason: Error Message: llerKind="OpenStackMachine" worker count=10 I0709 17:43:20.110457 1 controller.go:286] "Starting Controller" controller="openstackserver" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackServer" I0709 17:43:20.110500 1 controller.go:289] "Starting workers" controller="openstackserver" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackServer" worker count=10 I0709 17:43:20.110592 1 controller.go:286] "Starting Controller" controller="openstackfloatingippool" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackFloatingIPPool" I0709 17:43:20.110610 1 controller.go:289] "Starting workers" controller="openstackfloatingippool" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackFloatingIPPool" worker count=1 E0709 17:43:54.886533 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 E0709 17:43:59.889584 1 leaderelection.go:448] error retrieving resource lock capo-system/controller-leader-election-capo: the server was unable to return a response in the time allotted, but may still be processing the request (get leases.coordination.k8s.io controller-leader-election-capo) I0709 17:43:59.889619 1 leaderelection.go:297] failed to renew lease capo-system/controller-leader-election-capo: context deadline exceeded E0709 17:44:04.890580 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) E0709 17:44:04.890716 1 main.go:304] "problem running manager" err="leader election lost" logger="setup" Exit Code: 1 Started: Thu, 09 Jul 2026 17:42:53 +0000 Finished: Thu, 09 Jul 2026 17:44:53 +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-gc7k2 (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-gc7k2: 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 36m default-scheduler Successfully assigned capo-system/capo-controller-manager-56cf844ccd-xqhzg to instance Normal Killing 32m kubelet Container manager failed liveness probe, will be restarted Normal Pulled 32m (x2 over 36m) kubelet Container image "harbor.atmosphere.dev/registry.k8s.io/capi-openstack/capi-openstack-controller:v0.14.4" already present on machine Warning Unhealthy 32m (x3 over 36m) kubelet Readiness probe failed: Get "http://10.0.0.192:9440/readyz": dial tcp 10.0.0.192:9440: connect: connection refused Normal Created 32m (x2 over 36m) kubelet Created container manager Normal Started 32m (x2 over 36m) kubelet Started container manager Warning Unhealthy 30m (x6 over 33m) kubelet Liveness probe failed: Get "http://10.0.0.192:9440/healthz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Warning Unhealthy 30m (x10 over 33m) kubelet Readiness probe failed: Get "http://10.0.0.192:9440/readyz": context deadline exceeded (Client.Timeout exceeded while awaiting headers)