openshift / openshift/machine-config-operator
tracker for: Marking Degraded due to: machineconfig.machineconfiguration.openshift.io "rendered-..." not found
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 269
- Forks
- 529
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 83
Description
This almost always happens when you're providing some sort of "day 1" configuration that causes the "bootstrap" machineconfig to differ from the "in cluster" rendered configuration.
The MCO has had numerous bugs in this area in the past. Examples:
In order to debug this, we need more information about the cluster configuration - a full must gather, or at least the platform and any specific customizations you're doing.
Contributor guide
No contributing guide indexed for this repository
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 reviewing the bootstrap versus in-cluster rendered MachineConfig difference described in the issue and the related pull request #2108. Collect a full must-gather, or at least the platform and customizations, to reproduce and narrow the degraded state. Done means identifying the configuration mismatch and a concrete fix or follow-up.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100