Fix encrypt_lvm test module fail on Leap 42.3 #6777
Merged
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
The test failed because Leap 42.3 used steps for Libstorage-NG, though it is using Libstorage. The commit adds an appropriate distri provider for Leap 42.3.
OleksandrOrlov
force-pushed
the
47426_fix_leap_42_encrypt_lvm
branch
from
505e1f1
to
c149156
Compare
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.
For reviewers: please merge the needles first.
The test failed because Leap 42.3 used steps for Libstorage-NG, though
it is using Libstorage.
The commit adds an appropriate distri provider for Leap 42.3.