Name: capo-controller-manager-65565fdb7f-v5dc9 Namespace: capo-system Priority: 0 Service Account: capo-manager Node: instance/199.204.45.44 Start Time: Sat, 09 May 2026 22:30:44 +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.124 IPs: IP: 10.0.0.124 Controlled By: ReplicaSet/capo-controller-manager-65565fdb7f Containers: manager: Container ID: containerd://5dbb862d972a01e51d9fe5bd6d747dc62ec69e6d1c0cf721da57e9a6b920d407 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 22:35:58 +0000 Last State: Terminated Reason: Error Message: 22:35:04.953631 1 reflector.go:368] Caches populated for *v1beta1.Machine from pkg/mod/k8s.io/client-go@v0.31.14/tools/cache/reflector.go:243 I0509 22:35:04.953760 1 reflector.go:368] Caches populated for *v1alpha1.OpenStackFloatingIPPool from pkg/mod/k8s.io/client-go@v0.31.14/tools/cache/reflector.go:243 I0509 22:35:04.956171 1 reflector.go:368] Caches populated for *v1alpha1.Image from pkg/mod/k8s.io/client-go@v0.31.14/tools/cache/reflector.go:243 I0509 22:35:05.046107 1 controller.go:217] "Starting workers" controller="openstackfloatingippool" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackFloatingIPPool" worker count=1 I0509 22:35:05.046243 1 controller.go:217] "Starting workers" controller="openstackcluster" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackCluster" worker count=10 I0509 22:35:05.055494 1 controller.go:217] "Starting workers" controller="openstackmachine" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackMachine" worker count=10 I0509 22:35:05.055698 1 controller.go:217] "Starting workers" controller="openstackserver" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackServer" worker count=10 E0509 22:35:28.552103 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 22:35:33.552092 1 leaderelection.go:472] Failed to update 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 I0509 22:35:33.552149 1 leaderelection.go:297] failed to renew lease capo-system/controller-leader-election-capo: timed out waiting for the condition E0509 22:35:35.346513 1 main.go:281] "problem running manager" err="leader election lost" logger="setup" Exit Code: 1 Started: Sat, 09 May 2026 22:34:47 +0000 Finished: Sat, 09 May 2026 22:35:55 +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-msnbd (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-msnbd: 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 31m default-scheduler Successfully assigned capo-system/capo-controller-manager-65565fdb7f-v5dc9 to instance Warning Unhealthy 28m kubelet Liveness probe failed: Get "http://10.0.0.124:9440/healthz": read tcp 10.0.0.211:44640->10.0.0.124:9440: read: connection reset by peer Warning Unhealthy 28m kubelet Readiness probe failed: Get "http://10.0.0.124:9440/readyz": read tcp 10.0.0.211:44648->10.0.0.124:9440: read: connection reset by peer Warning Unhealthy 28m (x2 over 28m) kubelet Liveness probe failed: Get "http://10.0.0.124:9440/healthz": dial tcp 10.0.0.124:9440: connect: connection refused Normal Killing 28m kubelet Container manager failed liveness probe, will be restarted Warning Unhealthy 27m (x4 over 28m) kubelet Readiness probe failed: Get "http://10.0.0.124:9440/readyz": dial tcp 10.0.0.124:9440: connect: connection refused Warning Unhealthy 26m kubelet Readiness probe failed: Get "http://10.0.0.124:9440/readyz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Warning Unhealthy 26m kubelet Liveness probe failed: Get "http://10.0.0.124:9440/healthz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Warning Unhealthy 26m kubelet Liveness probe failed: Get "http://10.0.0.124:9440/healthz": read tcp 10.0.0.211:57524->10.0.0.124:9440: read: connection reset by peer Warning Unhealthy 26m kubelet Readiness probe failed: Get "http://10.0.0.124:9440/readyz": read tcp 10.0.0.211:57530->10.0.0.124:9440: read: connection reset by peer Normal Started 26m (x3 over 31m) kubelet Started container manager Normal Created 26m (x3 over 31m) kubelet Created container manager Normal Pulled 26m (x3 over 31m) kubelet Container image "harbor.atmosphere.dev/registry.k8s.io/capi-openstack/capi-openstack-controller:v0.12.7" already present on machine