Do not raise exception if can't get PV free space #755
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
Also use the cached PV info instead of running pvinfo again. Related: rhbz#1676718
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.
Also use the cached PV info instead of running pvinfo again.
Related: rhbz#1676718
The main reason for this change is to fix anaconda crash on systems with a cluster VG.
pvson these systems won't show information about the "cluster" PV, but we still know it is a PV from udev (because it has lvmpv signature) and we are trying to get additional information about. I think it should be safe to just setfreeto 0 (the PV is not really usable) and log error.