anaconda.git/pyanaconda/storage/errors.py, branch firstboot-support

Remove the storage module and replace it with blivet.

2013-01-28T19:15:31+00:00

Remove filesystem migration code.

2013-01-28T19:13:11+00:00

The only time anyone really used it was to migrate from ext2->ext3.
It is dead weight.

Add error handling around significant ui-initiated storage operations.

2012-09-11T19:44:12+00:00

If automatic partitioning fails, we reset the storage instance to its
prior state. The custom spoke operates on a copy of the storage
instance, so that means it gets reset to whatever the state was upon
entering the custom spoke. For the storage spoke we have little choice
but to actually call self.storage.reset() which actually re-scans the
devices.

For other operations within the custom spoke, the goal is to restore
things to the state prior to the failed action. If that fails, the
custom spoke will simply reset its storage instance as described above
for automatic partitioning failures.

Improve error granularity slightly in automatic partitioning.

2012-09-11T19:44:12+00:00

Also remove unused PartitioningWarning exception.

Merge branch 'master' into newui-merge

2012-06-20T22:34:11+00:00

Conflicts:
	Makefile.am
	anaconda
	anaconda.spec.in
	loader/loader.c
	loader/net.c
	loader/unpack.c
	po/POTFILES.in
	pyanaconda/__init__.py
	pyanaconda/bootloader.py
	pyanaconda/cmdline.py
	pyanaconda/constants.py
	pyanaconda/dispatch.py
	pyanaconda/errors.py
	pyanaconda/flags.py
	pyanaconda/iutil.py
	pyanaconda/kickstart.py
	pyanaconda/platform.py
	pyanaconda/storage/__init__.py
	pyanaconda/storage/devicetree.py
	pyanaconda/storage/fcoe.py
	pyanaconda/storage/formats/swap.py
	pyanaconda/storage/iscsi.py
	pyanaconda/storage/partitioning.py
	pyanaconda/yuminstall.py
	scripts/makeupdates

Add missing definition of BTRFSError. (#796013)

2012-02-24T15:35:42+00:00

Remove the anaconda attribute from Storage and add a bootloader attr.

2012-02-09T21:39:49+00:00

The main thing we used the anaconda attribute for was access to the
installer's user interface. The approach taken in this patch is to
replace direct usage of a user interface library with optional error
callbacks. The callbacks take an Exception instance and, in some
cases, a StorageDevice instance as arguments. They can display pop-
up windows or whatever they want to do. A return value of True
indicates that the error was fatal. In this case the exception is
raised.

Storage should not be interactive when building the device tree.

2011-11-22T15:44:14+00:00

This patch has the following set backs (for now):

(1) All the inconsistent LVM, RAID, and uninitialized disk dialogs are gone.
    They will not be coming back in this format.  Instead, I am planning on
    prompting for this sort of information on an as-needed basis when disks
    are selected for installation during the storage spokes.

(2) DASDs will not be formatted, though the code remains behind to do so.  For
    now it's still taking an intf argument but it's always going to be None.
    Again, I'm planning on doing this as-needed.  I did not remove the format
    code because it looks like it will be useful.

(3) Encrypted devices will not be added to the device tree because we can't
    prompt for the key.  I'm not yet sure what to do about this, but it will
    likely take the shape of scanning these devices separately later should
    they ever need to be used.

Show error dialog instead of traceback on fstab type mismatch. (#649171)

2011-09-30T16:42:59+00:00

It's a fatal error either way, but showing a popup is nicer than
crashing.

Do not traceback on mpath errors caused by faulty hardware.

2011-07-25T12:16:26+00:00

Resolves: rhbz#689520