Name: capo-controller-manager-78487c64cd-qc7w6 Namespace: capo-system Priority: 0 Service Account: capo-manager Node: instance/199.204.45.129 Start Time: Tue, 19 May 2026 20:02:44 +0000 Labels: cluster.x-k8s.io/provider=infrastructure-openstack control-plane=capo-controller-manager pod-template-hash=78487c64cd Annotations: Status: Running SeccompProfile: RuntimeDefault IP: 10.0.0.34 IPs: IP: 10.0.0.34 Controlled By: ReplicaSet/capo-controller-manager-78487c64cd Containers: manager: Container ID: containerd://2f48e05f93429a5ca2e81c2b8286026129618d9b5102575e7cd05f613892347c 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: Tue, 19 May 2026 20:05:09 +0000 Last State: Terminated Reason: Error Message: or *v1alpha1.Image from pkg/mod/k8s.io/client-go@v0.31.14/tools/cache/reflector.go:243 I0519 20:02:50.040260 1 controller.go:217] "Starting workers" controller="openstackmachine" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackMachine" worker count=10 I0519 20:02:50.040410 1 controller.go:217] "Starting workers" controller="openstackcluster" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackCluster" worker count=10 I0519 20:02:50.040701 1 controller.go:217] "Starting workers" controller="openstackfloatingippool" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackFloatingIPPool" worker count=1 I0519 20:02:50.042948 1 controller.go:217] "Starting workers" controller="openstackserver" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackServer" worker count=10 E0519 20:03:27.764137 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 E0519 20:03:32.763807 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 I0519 20:03:32.763923 1 leaderelection.go:297] failed to renew lease capo-system/controller-leader-election-capo: timed out waiting for the condition E0519 20:03:37.765047 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) E0519 20:03:37.765297 1 main.go:281] "problem running manager" err="leader election lost" logger="setup" Exit Code: 1 Started: Tue, 19 May 2026 20:02:49 +0000 Finished: Tue, 19 May 2026 20:03:37 +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: Mounts: /tmp/k8s-webhook-server/serving-certs from cert (ro) /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-lgxcs (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-lgxcs: 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: 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 3m25s default-scheduler Successfully assigned capo-system/capo-controller-manager-78487c64cd-qc7w6 to instance Warning FailedMount 3m25s kubelet MountVolume.SetUp failed for volume "cert" : secret "capo-webhook-service-cert" not found Normal Pulling 3m24s kubelet Pulling image "harbor.atmosphere.dev/registry.k8s.io/capi-openstack/capi-openstack-controller:v0.12.7" Normal Pulled 3m20s kubelet Successfully pulled image "harbor.atmosphere.dev/registry.k8s.io/capi-openstack/capi-openstack-controller:v0.12.7" in 1.534s (3.688s including waiting) Warning Unhealthy 2m4s (x3 over 2m24s) kubelet Liveness probe failed: Get "http://10.0.0.34:9440/healthz": dial tcp 10.0.0.34:9440: connect: connection refused Normal Killing 2m4s kubelet Container manager failed liveness probe, will be restarted Warning Unhealthy 64s (x10 over 2m24s) kubelet Readiness probe failed: Get "http://10.0.0.34:9440/readyz": dial tcp 10.0.0.34:9440: connect: connection refused Normal Created 61s (x2 over 3m20s) kubelet Created container manager Normal Pulled 61s kubelet Container image "harbor.atmosphere.dev/registry.k8s.io/capi-openstack/capi-openstack-controller:v0.12.7" already present on machine Normal Started 60s (x2 over 3m20s) kubelet Started container manager Warning Unhealthy 56s (x3 over 58s) kubelet Readiness probe failed: Get "http://10.0.0.34:9440/readyz": context deadline exceeded (Client.Timeout exceeded while awaiting headers)