Name: capo-controller-manager-6975759b4b-h4qc9 Namespace: capo-system Priority: 0 Service Account: capo-manager Node: instance/162.253.55.207 Start Time: Tue, 31 Mar 2026 05:49:03 +0000 Labels: cluster.x-k8s.io/provider=infrastructure-openstack control-plane=capo-controller-manager pod-template-hash=6975759b4b Annotations: Status: Running SeccompProfile: RuntimeDefault IP: 10.0.0.209 IPs: IP: 10.0.0.209 Controlled By: ReplicaSet/capo-controller-manager-6975759b4b Containers: manager: Container ID: containerd://1b6d6d27a755104173d397ebe0448feb0be31a3a657699b03020b89dd2aa3e68 Image: harbor.atmosphere.dev/registry.k8s.io/capi-openstack/capi-openstack-controller:v0.12.4 Image ID: harbor.atmosphere.dev/registry.k8s.io/capi-openstack/capi-openstack-controller@sha256:237da708e483aa8c39766a217d25e45de52816d446764569c77550e6f56f0970 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: Tue, 31 Mar 2026 05:55:44 +0000 Last State: Terminated Reason: Error Message: or.go:243 I0331 05:53:33.038122 1 reflector.go:368] Caches populated for *v1beta1.OpenStackMachine from pkg/mod/k8s.io/client-go@v0.31.10/tools/cache/reflector.go:243 I0331 05:53:33.135259 1 controller.go:217] "Starting workers" controller="openstackcluster" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackCluster" worker count=10 I0331 05:53:33.135777 1 controller.go:217] "Starting workers" controller="openstackmachine" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackMachine" worker count=10 I0331 05:53:33.135772 1 controller.go:217] "Starting workers" controller="openstackfloatingippool" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackFloatingIPPool" worker count=1 I0331 05:53:33.135835 1 controller.go:217] "Starting workers" controller="openstackserver" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackServer" worker count=10 E0331 05:54:10.772677 1 leaderelection.go:429] Failed to update lock optimitically: the server was unable to return a response in the time allotted, but may still be processing the request (put leases.coordination.k8s.io controller-leader-election-capo), falling back to slow path E0331 05:54:15.769598 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": context deadline exceeded I0331 05:54:15.769643 1 leaderelection.go:297] failed to renew lease capo-system/controller-leader-election-capo: timed out waiting for the condition E0331 05:54:20.770358 1 leaderelection.go:322] Failed to release 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 E0331 05:54:20.770465 1 main.go:281] "problem running manager" err="leader election lost" logger="setup" Exit Code: 1 Started: Tue, 31 Mar 2026 05:53:14 +0000 Finished: Tue, 31 Mar 2026 05:54:20 +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-h7r94 (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-h7r94: 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 7m20s default-scheduler Successfully assigned capo-system/capo-controller-manager-6975759b4b-h4qc9 to instance Normal Pulled 3m10s (x2 over 7m20s) kubelet Container image "harbor.atmosphere.dev/registry.k8s.io/capi-openstack/capi-openstack-controller:v0.12.4" already present on machine Normal Created 3m10s (x2 over 7m20s) kubelet Created container manager Normal Started 3m10s (x2 over 7m20s) kubelet Started container manager Warning Unhealthy 100s (x6 over 4m20s) kubelet Liveness probe failed: Get "http://10.0.0.209:9440/healthz": dial tcp 10.0.0.209:9440: connect: connection refused Warning Unhealthy 100s (x12 over 4m20s) kubelet Readiness probe failed: Get "http://10.0.0.209:9440/readyz": dial tcp 10.0.0.209:9440: connect: connection refused Normal Killing 100s (x2 over 4m) kubelet Container manager failed liveness probe, will be restarted