Name: capo-controller-manager-65565fdb7f-x6fq5 Namespace: capo-system Priority: 0 Service Account: capo-manager Node: instance/199.204.45.74 Start Time: Sat, 09 May 2026 05:59:54 +0000 Labels: cluster.x-k8s.io/provider=infrastructure-openstack control-plane=capo-controller-manager pod-template-hash=65565fdb7f Annotations: Status: Running SeccompProfile: RuntimeDefault IP: 10.0.0.186 IPs: IP: 10.0.0.186 Controlled By: ReplicaSet/capo-controller-manager-65565fdb7f Containers: manager: Container ID: containerd://2c21c545b6ad89dc007abf3e9ea144fba542d3d7a0cd943fde6f3a2dc8b35395 Image: harbor.atmosphere.dev/registry.k8s.io/capi-openstack/capi-openstack-controller:v0.12.7 Image ID: harbor.atmosphere.dev/registry.k8s.io/capi-openstack/capi-openstack-controller@sha256:b964c2f374ad4f26a593749d3c737492d5c1821db143b26596c9285b9055a8b4 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 State: Running Started: Sat, 09 May 2026 06:04:44 +0000 Last State: Terminated Reason: Error Message: Caches populated for *v1alpha1.Image from pkg/mod/k8s.io/client-go@v0.31.14/tools/cache/reflector.go:243 I0509 06:00:06.984580 1 controller.go:217] "Starting workers" controller="openstackfloatingippool" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackFloatingIPPool" worker count=1 I0509 06:00:06.989719 1 controller.go:217] "Starting workers" controller="openstackcluster" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackCluster" worker count=10 I0509 06:00:06.989892 1 controller.go:217] "Starting workers" controller="openstackmachine" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackMachine" worker count=10 I0509 06:00:06.992212 1 controller.go:217] "Starting workers" controller="openstackserver" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackServer" worker count=10 E0509 06:04:14.398339 1 leaderelection.go:429] Failed to update lock optimitically: 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 E0509 06:04:19.398811 1 leaderelection.go:436] 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) I0509 06:04:19.399819 1 leaderelection.go:297] failed to renew lease capo-system/controller-leader-election-capo: timed out waiting for the condition E0509 06:04:20.110372 1 leaderelection.go:322] Failed to release lock: Operation cannot be fulfilled on leases.coordination.k8s.io "controller-leader-election-capo": the object has been modified; please apply your changes to the latest version and try again E0509 06:04:20.110486 1 main.go:281] "problem running manager" err="leader election lost" logger="setup" Exit Code: 1 Started: Sat, 09 May 2026 05:59:55 +0000 Finished: Sat, 09 May 2026 06:04:25 +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-mgnmn (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-mgnmn: 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-65565fdb7f-x6fq5 to instance Warning Unhealthy 30m kubelet Liveness probe failed: Get "http://10.0.0.186:9440/healthz": read tcp 10.0.0.205:54976->10.0.0.186:9440: read: connection reset by peer Warning Unhealthy 30m kubelet Readiness probe failed: Get "http://10.0.0.186:9440/readyz": read tcp 10.0.0.205:54992->10.0.0.186:9440: read: connection reset by peer Normal Pulled 30m (x2 over 34m) kubelet Container image "harbor.atmosphere.dev/registry.k8s.io/capi-openstack/capi-openstack-controller:v0.12.7" already present on machine Normal Created 30m (x2 over 34m) kubelet Created container manager Normal Started 30m (x2 over 34m) kubelet Started container manager Warning Unhealthy 30m (x2 over 30m) kubelet Liveness probe failed: Get "http://10.0.0.186:9440/healthz": dial tcp 10.0.0.186:9440: connect: connection refused Warning Unhealthy 30m (x3 over 30m) kubelet Readiness probe failed: Get "http://10.0.0.186:9440/readyz": dial tcp 10.0.0.186:9440: connect: connection refused Normal Killing 30m kubelet Container manager failed liveness probe, will be restarted