Name: capo-controller-manager-6975759b4b-c7lpc Namespace: capo-system Priority: 0 Service Account: capo-manager Node: instance/199.204.45.53 Start Time: Tue, 14 Apr 2026 08:15:59 +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.132 IPs: IP: 10.0.0.132 Controlled By: ReplicaSet/capo-controller-manager-6975759b4b Containers: manager: Container ID: containerd://6d48e5e42c599d95608b3e16e83ff687f258085a451d774882043fa44ccbdc80 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, 14 Apr 2026 08:22:17 +0000 Last State: Terminated Reason: Error Message: or *v1alpha1.Image from pkg/mod/k8s.io/client-go@v0.31.10/tools/cache/reflector.go:243 I0414 08:20:47.114141 1 controller.go:217] "Starting workers" controller="openstackcluster" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackCluster" worker count=10 I0414 08:20:47.117471 1 controller.go:217] "Starting workers" controller="openstackmachine" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackMachine" worker count=10 I0414 08:20:47.117585 1 controller.go:217] "Starting workers" controller="openstackfloatingippool" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackFloatingIPPool" worker count=1 I0414 08:20:47.120759 1 controller.go:217] "Starting workers" controller="openstackserver" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackServer" worker count=10 E0414 08:21:19.626858 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": net/http: request canceled (Client.Timeout exceeded while awaiting headers), falling back to slow path E0414 08:21:24.626257 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 I0414 08:21:24.626313 1 leaderelection.go:297] failed to renew lease capo-system/controller-leader-election-capo: timed out waiting for the condition E0414 08:21:29.627226 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": net/http: request canceled (Client.Timeout exceeded while awaiting headers) E0414 08:21:29.627343 1 main.go:281] "problem running manager" err="leader election lost" logger="setup" Exit Code: 1 Started: Tue, 14 Apr 2026 08:20:22 +0000 Finished: Tue, 14 Apr 2026 08:22:12 +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-tbrhg (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-tbrhg: 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 40m default-scheduler Successfully assigned capo-system/capo-controller-manager-6975759b4b-c7lpc to instance Warning Unhealthy 37m (x3 over 37m) kubelet Liveness probe failed: Get "http://10.0.0.132:9440/healthz": dial tcp 10.0.0.132:9440: connect: connection refused Normal Pulled 36m (x2 over 40m) kubelet Container image "harbor.atmosphere.dev/registry.k8s.io/capi-openstack/capi-openstack-controller:v0.12.4" already present on machine Warning Unhealthy 36m (x8 over 37m) kubelet Readiness probe failed: Get "http://10.0.0.132:9440/readyz": dial tcp 10.0.0.132:9440: connect: connection refused Normal Created 36m (x2 over 40m) kubelet Created container manager Normal Started 36m (x2 over 40m) kubelet Started container manager Normal Killing 34m (x2 over 37m) kubelet Container manager failed liveness probe, will be restarted Warning Unhealthy 34m (x3 over 35m) kubelet Liveness probe failed: Get "http://10.0.0.132:9440/healthz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Warning Unhealthy 34m (x4 over 35m) kubelet Readiness probe failed: Get "http://10.0.0.132:9440/readyz": context deadline exceeded (Client.Timeout exceeded while awaiting headers)