tests: Rescan vdevs after lvm raid tests #1168
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
|
Jenkins, test this please. |
tbzatek
force-pushed
the
lvm-raid-tests-2
branch
from
93e79e8
to
ed691d5
Compare
vojtechtrefny
approved these changes
Aug 9, 2023
Device names might change after scsi host rescan and our vdevs need to be populated again.
tbzatek
force-pushed
the
lvm-raid-tests-2
branch
from
5f59b92
to
d1c5c78
Compare
|
Jenkins, test this please. |
vojtechtrefny
approved these changes
Sep 6, 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.
Device names might change after scsi host rescan and our vdevs need to be populated again.
This is a rather dirty hack and thefindmatching looks fragile. Would be nice to query udevdb directly perhaps, or query udisks even? None of those are 100% reliable.