Skip to content
This repository has been archived by the owner on Mar 31, 2023. It is now read-only.

ensure initial master has associated plan so it will not be re-provisioned #118

Merged

Conversation

jrryjcksn
Copy link
Contributor

It's possible for an update to come in for the initial master before the first other node is created by the controller. If this happens, the initial master has not yet had a plan assigned so the controller updates it (the controller compares old and new plans to determine if a node must be updated). This PR ensures that the initial master has a plan before allowing any updates to occur.

@jrryjcksn jrryjcksn self-assigned this Jan 15, 2020
Copy link
Contributor

@dimitropoulos dimitropoulos left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

#findofthecentury

@jrryjcksn
Copy link
Contributor Author

Thanks for the review!

@jrryjcksn jrryjcksn merged commit 352a07d into master Jan 15, 2020
@jrryjcksn jrryjcksn deleted the 2020-1-15-fix-for-ignite-firekube-cluster-creation-bug branch January 15, 2020 16:19
D3nn pushed a commit that referenced this pull request May 8, 2020
…ioned (#118)

Co-authored-by: weave-e2e-quickstart <58864910+weave-e2e-quickstart@users.noreply.github.com>
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants