Name: capo-controller-manager-6975759b4b-97lrd Namespace: capo-system Priority: 0 Service Account: capo-manager Node: instance/199.204.45.229 Start Time: Wed, 04 Mar 2026 02:13:29 +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.181 IPs: IP: 10.0.0.181 Controlled By: ReplicaSet/capo-controller-manager-6975759b4b Containers: manager: Container ID: containerd://5cd4bb9f634aa19636abb50f9b529dcc1f3dabd7b85330b0eac9574a5630bf5e 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: Wed, 04 Mar 2026 02:20:53 +0000 Last State: Terminated Reason: Error Message: "Starting workers" controller="openstackserver" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="OpenStackServer" worker count=10 E0304 02:19:14.495924 1 event.go:359] "Server rejected event (will not retry!)" err="etcdserver: request timed out" event="&Event{ObjectMeta:{controller-leader-election-capo.189981e4ac2c6c1d 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:d22c1363-313b-4425-ba35-b867d0197249,APIVersion:coordination.k8s.io/v1,ResourceVersion:24051,FieldPath:,},Reason:LeaderElection,Message:capo-controller-manager-6975759b4b-97lrd_7880fa81-2931-48e3-ba09-8eb37d3d9263 became leader,Source:EventSource{Component:capo-controller-manager-6975759b4b-97lrd_7880fa81-2931-48e3-ba09-8eb37d3d9263,Host:,},FirstTimestamp:2026-03-04 02:19:07.488119837 +0000 UTC m=+35.286701385,LastTimestamp:2026-03-04 02:19:07.488119837 +0000 UTC m=+35.286701385,Count:1,Type:Normal,EventTime:0001-01-01 00:00:00 +0000 UTC,Series:nil,Action:,Related:nil,ReportingController:capo-controller-manager-6975759b4b-97lrd_7880fa81-2931-48e3-ba09-8eb37d3d9263,ReportingInstance:,}" E0304 02:19:31.067992 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 E0304 02:19:36.068205 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 I0304 02:19:36.068291 1 leaderelection.go:297] failed to renew lease capo-system/controller-leader-election-capo: timed out waiting for the condition E0304 02:19:37.448210 1 main.go:281] "problem running manager" err="leader election lost" logger="setup" Exit Code: 1 Started: Wed, 04 Mar 2026 02:18:32 +0000 Finished: Wed, 04 Mar 2026 02:19:51 +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-9zfd4 (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-9zfd4: 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 37m default-scheduler Successfully assigned capo-system/capo-controller-manager-6975759b4b-97lrd to instance Warning Unhealthy 34m (x3 over 34m) kubelet Liveness probe failed: Get "http://10.0.0.181:9440/healthz": dial tcp 10.0.0.181:9440: connect: connection refused Normal Killing 34m kubelet Container manager failed liveness probe, will be restarted Normal Pulled 33m (x2 over 37m) kubelet Container image "harbor.atmosphere.dev/registry.k8s.io/capi-openstack/capi-openstack-controller:v0.12.4" already present on machine Warning Unhealthy 32m (x13 over 34m) kubelet Readiness probe failed: Get "http://10.0.0.181:9440/readyz": dial tcp 10.0.0.181:9440: connect: connection refused Normal Created 32m (x2 over 37m) kubelet Created container manager Normal Started 32m (x2 over 37m) kubelet Started container manager Warning Unhealthy 31m kubelet Liveness probe failed: Get "http://10.0.0.181:9440/healthz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Warning Unhealthy 31m (x2 over 31m) kubelet Readiness probe failed: Get "http://10.0.0.181:9440/readyz": context deadline exceeded (Client.Timeout exceeded while awaiting headers)