Name: orc-controller-manager-6cb597b5d4-8ss2s Namespace: orc-system Priority: 0 Service Account: orc-controller-manager Node: instance/199.204.45.65 Start Time: Wed, 27 May 2026 10:40:09 +0000 Labels: control-plane=controller-manager pod-template-hash=6cb597b5d4 Annotations: kubectl.kubernetes.io/default-container: manager Status: Running SeccompProfile: RuntimeDefault IP: 10.0.0.246 IPs: IP: 10.0.0.246 Controlled By: ReplicaSet/orc-controller-manager-6cb597b5d4 Containers: manager: Container ID: containerd://5547801bc234ee524bed20d1919d88badbbf85d86a72e6fc1d027afe17617f7b Image: harbor.atmosphere.dev/quay.io/orc/openstack-resource-controller:v2.2.0 Image ID: harbor.atmosphere.dev/quay.io/orc/openstack-resource-controller@sha256:e3c51b1c3048c3f8c2856a6327810981fd4624602091021c4d310092c85e247c Port: Host Port: Command: /manager Args: --metrics-bind-address=:8443 --leader-elect --health-probe-bind-address=:8081 State: Running Started: Wed, 27 May 2026 10:46:26 +0000 Last State: Terminated Reason: Error Message: ailed to update lock optimistically: Put "https://10.96.0.1:443/apis/coordination.k8s.io/v1/namespaces/orc-system/leases/f35396c5.k-orc.cloud?timeout=5s": context deadline exceeded, falling back to slow path E0527 10:45:39.684882 1 event.go:359] "Server rejected event (will not retry!)" err="etcdserver: request timed out" event="&Event{ObjectMeta:{f35396c5.k-orc.cloud.18b36646f46e2936 orc-system 0 0001-01-01 00:00:00 +0000 UTC map[] map[] [] [] []},InvolvedObject:ObjectReference{Kind:Lease,Namespace:orc-system,Name:f35396c5.k-orc.cloud,UID:29bdae39-ffd9-49ac-8cf7-a45972f85d48,APIVersion:coordination.k8s.io/v1,ResourceVersion:25126,FieldPath:,},Reason:LeaderElection,Message:orc-controller-manager-6cb597b5d4-8ss2s_fd19260a-f8b8-48e5-b6a0-71d68d69371a became leader,Source:EventSource{Component:orc-controller-manager-6cb597b5d4-8ss2s_fd19260a-f8b8-48e5-b6a0-71d68d69371a,Host:,},FirstTimestamp:2026-05-27 10:45:32.676081974 +0000 UTC m=+23.955037355,LastTimestamp:2026-05-27 10:45:32.676081974 +0000 UTC m=+23.955037355,Count:1,Type:Normal,EventTime:0001-01-01 00:00:00 +0000 UTC,Series:nil,Action:,Related:nil,ReportingController:orc-controller-manager-6cb597b5d4-8ss2s_fd19260a-f8b8-48e5-b6a0-71d68d69371a,ReportingInstance:,}" E0527 10:45:42.677196 1 leaderelection.go:472] Failed to update lock: Put "https://10.96.0.1:443/apis/coordination.k8s.io/v1/namespaces/orc-system/leases/f35396c5.k-orc.cloud?timeout=5s": context deadline exceeded I0527 10:45:42.677261 1 leaderelection.go:297] failed to renew lease orc-system/f35396c5.k-orc.cloud: context deadline exceeded E0527 10:45:47.678203 1 leaderelection.go:322] Failed to release lock: Put "https://10.96.0.1:443/apis/coordination.k8s.io/v1/namespaces/orc-system/leases/f35396c5.k-orc.cloud?timeout=5s": context deadline exceeded 2026-05-27T10:45:47Z ERROR setup Error starting manager {"error": "problem running manager: leader election lost"} main.main /workspace/cmd/manager/main.go:121 runtime.main /usr/local/go/src/runtime/proc.go:272 Exit Code: 1 Started: Wed, 27 May 2026 10:45:08 +0000 Finished: Wed, 27 May 2026 10:45:54 +0000 Ready: True Restart Count: 2 Limits: cpu: 500m memory: 256Mi Requests: cpu: 10m memory: 64Mi Liveness: http-get http://:8081/healthz delay=15s timeout=1s period=20s #success=1 #failure=3 Readiness: http-get http://:8081/readyz delay=5s timeout=1s period=10s #success=1 #failure=3 Environment: Mounts: /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-zrhd2 (ro) Conditions: Type Status Initialized True Ready True ContainersReady True PodScheduled True Volumes: kube-api-access-zrhd2: Type: Projected (a volume that contains injected data from multiple sources) TokenExpirationSeconds: 3607 ConfigMapName: kube-root-ca.crt ConfigMapOptional: DownwardAPI: true QoS Class: Burstable Node-Selectors: openstack-control-plane=enabled Tolerations: 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 38m default-scheduler Successfully assigned orc-system/orc-controller-manager-6cb597b5d4-8ss2s to instance Normal Pulling 38m kubelet Pulling image "harbor.atmosphere.dev/quay.io/orc/openstack-resource-controller:v2.2.0" Normal Pulled 38m kubelet Successfully pulled image "harbor.atmosphere.dev/quay.io/orc/openstack-resource-controller:v2.2.0" in 1.556s (1.556s including waiting) Warning Unhealthy 32m kubelet Liveness probe failed: Get "http://10.0.0.246:8081/healthz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Warning Unhealthy 32m kubelet Readiness probe failed: Get "http://10.0.0.246:8081/readyz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Warning Unhealthy 32m (x3 over 34m) kubelet Liveness probe failed: Get "http://10.0.0.246:8081/healthz": dial tcp 10.0.0.246:8081: connect: connection refused Warning Unhealthy 32m (x10 over 34m) kubelet Readiness probe failed: Get "http://10.0.0.246:8081/readyz": dial tcp 10.0.0.246:8081: connect: connection refused Normal Created 32m (x3 over 38m) kubelet Created container manager Normal Started 32m (x3 over 38m) kubelet Started container manager Normal Pulled 32m (x2 over 33m) kubelet Container image "harbor.atmosphere.dev/quay.io/orc/openstack-resource-controller:v2.2.0" already present on machine