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

fix: upgrade will now recreate the correct master #4637

Merged
merged 4 commits into from Sep 8, 2021

Conversation

deaborch
Copy link
Contributor

@deaborch deaborch commented Aug 31, 2021

Reason for Change:

Fix in Upgrade flow to recreate the correct missing master

Issue Fixed:

Fixes #4629

Problem occurs when the is a missing master in the upgrade process. The current implementation only recreates the first master at index (master-0) when there is a missing master node. This will cause upgrade to fail since the master it is trying to recreate already exists. This PR fixes that issue by finding the missing master and adding it to a map which will be checked and used to create the correct missing master at the correct index.
See steps to reproduce in the issue above.

Credit Where Due:

Does this change contain code from or inspired by another project?

  • No
  • Yes

If "Yes," did you notify that project's maintainers and provide attribution?

  • No
  • Yes

Requirements:

Notes:

Copy link
Member

@jackfrancis jackfrancis left a comment

Choose a reason for hiding this comment

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

/lgtm

@jackfrancis
Copy link
Member

Thanks for fixing this @deaborch! Confirmed that the current implementation indeed never does anything except to the first master:

https://play.golang.org/p/q5FtBfFgEU0

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.

Update always tries to recreate first master VM as opposed to creating the missing VM
3 participants