control plane node count increments too early during provisioning
- Dominant language
- Go
- Stars
- 2.1k
- Forks
- 328
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 9
Description
**What happened**:
Apparently out of sync messages in the logs during cluster creation. Let's take a 3-node control plane provisioning as an example.
During provisioning, the logs show messages like:
```
Scaling up control plane nodes, 3 expected (2 actual)","retries":367
```
But this is inaccurate in my opinion, because the `actual` counter increases the moment a node is being provisioned and not after it successfully comes up and acts as a control plane node :)
**What you expected to happen**:
The `actual` counter should only increment after a node is fully provisioned and functioning as a control plane node.
**How to reproduce it (as minimally and precisely as possible)**:
Create a cluster with a 3-node control plane and monitor the logs during provisioning. You will see the `actual` count incrementing early, even though the nodes aren't yet ready as control plane nodes.
**Anything else we need to know?**:
This can be misleading while watching provisioning progress or failures.
Contributor guide
Research direction
No file, test, or entry point is named in the issue. Start by locating the control-plane provisioning code that updates the actual node count, then reproduce a three-node control-plane creation and verify that the count changes only after nodes are fully provisioned and functioning.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100