Name: capo-controller-manager-65565fdb7f-t9hr9 Namespace: capo-system Priority: 0 Service Account: capo-manager Node: instance/199.204.45.246 Start Time: Fri, 29 May 2026 02:55:42 +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.247 IPs: IP: 10.0.0.247 Controlled By: ReplicaSet/capo-controller-manager-65565fdb7f Containers: manager: Container ID: containerd://8a82b87a8f27e9dc59b63878a877947a98f8f34f63b2778e56a989489020827d 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: Fri, 29 May 2026 03:00:36 +0000 Last State: Terminated Reason: Error Message: I0529 02:59:42.924009 1 controller.go:217] "Starting workers" controller="openstackserver" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackServer" worker count=10 E0529 02:59:47.816983 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 E0529 02:59:49.821400 1 event.go:359] "Server rejected event (will not retry!)" err="etcdserver: request timed out" event="&Event{ObjectMeta:{controller-leader-election-capo.18b3ea0481896ac3 capo-system 0 0001-01-01 00:00:00 +0000 UTC map[] map[] [] [] []},InvolvedObject:ObjectReference{Kind:Lease,Namespace:capo-system,Name:controller-leader-election-capo,UID:154ce9c2-3bf0-4295-8afc-ba8d1818249c,APIVersion:coordination.k8s.io/v1,ResourceVersion:25481,FieldPath:,},Reason:LeaderElection,Message:capo-controller-manager-65565fdb7f-t9hr9_eda21a72-0b15-4427-83d8-c7ab4706c905 became leader,Source:EventSource{Component:capo-controller-manager-65565fdb7f-t9hr9_eda21a72-0b15-4427-83d8-c7ab4706c905,Host:,},FirstTimestamp:2026-05-29 02:59:42.815513283 +0000 UTC m=+21.473450680,LastTimestamp:2026-05-29 02:59:42.815513283 +0000 UTC m=+21.473450680,Count:1,Type:Normal,EventTime:0001-01-01 00:00:00 +0000 UTC,Series:nil,Action:,Related:nil,ReportingController:capo-controller-manager-65565fdb7f-t9hr9_eda21a72-0b15-4427-83d8-c7ab4706c905,ReportingInstance:,}" E0529 02:59:52.817374 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 I0529 02:59:52.817459 1 leaderelection.go:297] failed to renew lease capo-system/controller-leader-election-capo: timed out waiting for the condition E0529 02:59:52.884491 1 main.go:281] "problem running manager" err="leader election lost" logger="setup" Exit Code: 1 Started: Fri, 29 May 2026 02:59:21 +0000 Finished: Fri, 29 May 2026 02:59:52 +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-kmw44 (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-kmw44: 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 32m default-scheduler Successfully assigned capo-system/capo-controller-manager-65565fdb7f-t9hr9 to instance Normal Created 29m (x2 over 32m) kubelet Created container manager Normal Started 29m (x2 over 32m) kubelet Started container manager Warning Unhealthy 29m kubelet Readiness probe failed: HTTP probe failed with statuscode: 500 Warning Unhealthy 28m (x6 over 29m) kubelet Liveness probe failed: Get "http://10.0.0.247:9440/healthz": dial tcp 10.0.0.247:9440: connect: connection refused Normal Killing 28m (x2 over 29m) kubelet Container manager failed liveness probe, will be restarted Warning Unhealthy 28m (x9 over 29m) kubelet Readiness probe failed: Get "http://10.0.0.247:9440/readyz": dial tcp 10.0.0.247:9440: connect: connection refused Normal Pulled 28m (x3 over 32m) kubelet Container image "harbor.atmosphere.dev/registry.k8s.io/capi-openstack/capi-openstack-controller:v0.12.7" already present on machine