spinframework / spinframework/spin-operator
Spin operator crashes with "leader election lost"
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 289
- Forks
- 34
- PR merge metrics
- No merged PRs in 30d
Description
2024-03-15T08:15:46Z DEBUG Reconciling Service {"controller": "spinapp", "controllerGroup": "core.spinoperator.dev", "controllerKind": "SpinApp", "SpinApp": {"name":"sentime │
│ E0315 08:17:36.395301 1 leaderelection.go:369] Failed to update lock: Put "https://10.43.0.1:443/apis/coordination.k8s.io/v1/namespaces/spin-operator/leases/90ba2d18.spinoperat │
│ I0315 08:17:36.395437 1 leaderelection.go:285] failed to renew lease spin-operator/90ba2d18.spinoperator.dev: timed out waiting for the condition │
│ 2024-03-15T08:17:36Z ERROR setup problem running manager {"error": "leader election lost"} │
│ main.main │
│ /workspace/cmd/main.go:143 │
│ runtime.main │
│ /usr/local/go/src/runtime/proc.go:271
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at cmd/main.go:143 and use the leader-election log sequence as the initial evidence. Investigate why the lease update times out in the Kubernetes environment, then verify that the operator manager no longer exits with “leader election lost” under the reproducing conditions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- distributed-systems, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100