[blivet+anaconda] handling for unusable storage configs

David Lehman dlehman at redhat.com
Wed Nov 5 15:49:13 UTC 2014


It is time to put to bed the notion that an OS installer must be able to
handle any imaginable garbage preexisting on system storage. The overall
idea is that there are some things we cannot handle in any reasonable way
without extensive UI. In those cases, the user must straighten things out
before proceeding.

The first patch is rendered mostly obsolete by the rest of the set, but it
follows how we handle the corresponding situation with md.

The second patch is intended to allow the use of ignoredisk (via kickstart)
to temporarily avoid dealing with a corrupt gpt disklabel.

There is no try/except around the storage resets in the storage spokes
because there is no reason to expect such a situation to arise anywhere
other than the initial scan or after a user-initiated re-scan.

It worked well for me in some testing with f21 for whatever that's worth.
Apparently I do not have the "QE knack".



More information about the anaconda-patches mailing list