I don't know. I'm not suggesting that this is the best or even an appropriate
solution, but I think the current behavior is problematic, especially in how it percolates
up to the user experience in Anaconda.
Maybe it's really not a blivet problem, and the fix is that anaconda should respond to
these errors by saying, "there was a problem scanning device <device>, do you
want to ignore the device, retry the scan, or fail?" or something (although in this
case blivet would probably need to provide better exceptions that make it easy to pull out
the failed device name).
Maybe blivet needs a an option to switch between device-failures-are-exceptions and
device-failures-are-logged, and in the latter case ignore both the device and anything
built on top of it.
--
To view this pull request on github, visit
https://github.com/rhinstaller/blivet/pull/227