Tests: Check cluster member names cannot be 'none' (stable-5.21) #14026
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
…'none' Signed-off-by: Julian Pelizäus <[email protected]> (cherry picked from commit c49ef5f)
… valid name Signed-off-by: Julian Pelizäus <[email protected]>
tomponline
approved these changes
Sep 2, 2024
tomponline
changed the title
|
Ta! |
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.
As we have both the password and token support in
5.21, we can completely backport c49ef5f.An additional commit ensures that also when joining cluster nodes using the legacy password (which is still in
5.21) the name cannot benone.This change works with the LXD snap from
5.21/edge.