[controller] Fix the migration_script bug with none LVMVolumeGroups labels #96
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
Signed-off-by: Viktor Kramarenko <[email protected]>
ViktorKram
changed the title
duckhawk
approved these changes
Sep 26, 2024
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.
Description
Fixed the error of migration_script, if some LVMVolumeGroup resource does not have any label.
Why do we need it, and what problem does it solve?
If a LVMVolumeGroup resource does not have any label, the migration script results into error every time and blocks sds-node-configurator deploying process.
What is the expected result?
Even if a LVMVolumeGroup resource does not have any label, the script and migration go fine.
Checklist