Fix master services list for etcd migration #6428
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We require that folks migrate to etcd v3 storage before upgrading to 3.7 and the 3.7 upgrade documentation also calls this out. So there's an incredibly strong chance that the 3.7 playbooks will be used to migrate from etcd v2 to v3. However in 3.6 if you had a single master it likely did not use the ha services. So check for that, this is slightly simplified logic copied from release-3.6 branch.