diff options
| author | Radek Vykydal <rvykydal@redhat.com> | 2009-06-05 08:56:29 +0200 |
|---|---|---|
| committer | Radek Vykydal <rvykydal@redhat.com> | 2009-06-05 09:11:30 +0200 |
| commit | 93fd07cd4cb46dad0d57bf216e603c8256751480 (patch) | |
| tree | ab0bb49d566e9f0c52fabeeafdc9bf026a3ec957 /Makefile | |
| parent | fee64fbdf603158229e371eaa848a3c44991c13a (diff) | |
| download | anaconda-93fd07cd4cb46dad0d57bf216e603c8256751480.tar.gz anaconda-93fd07cd4cb46dad0d57bf216e603c8256751480.tar.xz anaconda-93fd07cd4cb46dad0d57bf216e603c8256751480.zip | |
Fix discovery of existing raid/lvm for ks install without clearpart (#503310) (#503681)
Default clearPartType to None so that all devices are discovered during storage
initialization step, and UI parttype can be set to its default "Replace existing
linux system". Also set clearPartType appropriately when going back from partition dialog
so that all devices are discovered during storage reset.
There is one case that can't be resolved this way: clearpart --all or --linux
is set in ks and "Create custom layout" is selected in parttype UI step. Because of ks
setting, storage initialization doesn't discover devices (RAID, LVM) on
partitions that are to be cleared and therefore they are not present in custom
partition dialog. This can be workarounded by going back and than again to
custom partitioning dialog. I think we should grey-out type of partitioning
combo set to value from ks clearpart command.
Diffstat (limited to 'Makefile')
0 files changed, 0 insertions, 0 deletions