EKS-A Upgrade Validation Failed with observed generation != expected
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 2.1k
- Forks
- 328
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 9
Description
What happened:
Created workload cluster on a management cluster. Attempted to upgrade it, and observed the following error in preflight checks
2022-11-18T14:46:49.316-0500 V0 ❌ Validation failed {"validation": "upgrade preflight validations pass", "error": "validation failed with 1
errors: kubeadm control plane long-lived-drib-w-0 status needs to be refreshed: observed generation is 9, want 10", "remediation": ""}
and the operation failed. When I tried again later it succeeded.
What you expected to happen:
I would expect kubectl to retry if it has a stale reference to a K8s object, and EKS-A not to fail since there was nothing wrong with my cluster.
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:
- EKS Anywhere Release: 0.12.0 -> 0.12.1
- EKS Distro Release:
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 by tracing the upgrade preflight validation that emits the observed-generation error, then reproduce the workload-cluster upgrade from EKS Anywhere 0.12.0 to 0.12.1 if possible. Done means transiently stale Kubernetes object state no longer causes an otherwise valid upgrade to fail, with regression coverage for the validation behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100