UI cluster unseal bug #20897
Merged
UI cluster unseal bug #20897
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
hellobontempo
approved these changes
May 31, 2023
This was referenced May 31, 2023
zofskeez
added a commit
that referenced
this pull request
May 31, 2023
* fixes issue unsealing cloud seal type cluster * adds changelog entry
zofskeez
added a commit
that referenced
this pull request
May 31, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
It was discovered that the
secret_sharesandsecret_thresholdproperties are no longer allowed to be passed when unsealing a cloud seal type cluster. These properties were being passed in the UI causing the unseal to fail. Removing these properties from the payload for seal types other thanshamirallows the cluster to be unsealed as expected.Error before fix:
After fix:
Screen.Recording.2023-05-31.at.2.16.46.PM.mov
Resolves #20644