Update RAID array name after scheduling its creation #6185
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
Blivet can change the name for multiple reasons (invalid chars, name conflict etc.) so we need to make sure we have both the old and new name saved in case it is used in other kickstart commands like volgroup for example.
vojtechtrefny
temporarily deployed
to
gh-cockpituous
GitHub Actions
Inactive
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.
Blivet can change the name for multiple reasons (invalid chars,
name conflict etc.) so we need to make sure we have both the old
and new name saved in case it is used in other kickstart commands
like volgroup for example.
We already do the same for the volgroup command in
_execute_volgroup_data. This is currently blocked by related pykickstart fix for RAID names, see pykickstart/pykickstart#534