| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
(#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.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The i18n people have suggested using ngettext when we need to have
singular and plural forms of strings, where the count will vary as to
what we are reporting to the user.
I've made the changes they have suggested. I created a new lambda
function called P_() to use for the plural cases. P_() takes in three
parameters:
1) The singular form of the string.
2) The plural form of the string.
3) A count.
Here's an example:
....some loop runs doing stuff
bytesWritten = 47
msg = P_("Wrote %d byte.",
"Wrote %d bytes.",
bytesWritten) % (bytesWritten,)
print msg
The % substitution is correct at the end because P_() returns a single
string, so we only need the format string to account for that.
Some strings have been changed slightly to make it easier for
translations to other languages, particularly when choosing plural forms.
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
The use of a unique id frees us from having to worry about parted renaming
partitions whenever we remove one. It will also provide a mechanism with
which we can more reliably track protected partitions, currently
problematic for the same reason.
|
| |
|
|
|
|
| |
Since parted renames/renumbers partitions, we need to update the names
of the PartitionDevice instances so that they are in sync with the parted
Partition.
|
| |
|
|
|
| |
When calling udev_trigger for the save exception to local storage
device, limit the call to block devices.
|
| | |
|
| |
|
|
|
|
| |
For autopartitioning with live images, we want to make the fstype of
/ match that of the live image as otherwise, the partitioning
will fail due to the mismatch
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
It appears that the migratable property in the FS class was using
FS._isMigratable when we'd overridden that method in Ext3FS. This fix
prevents the upgrade migrate fs screen from showing up unless ext4migrate
is on the cmdline, like intended.
|
| |
|
|
|
|
|
| |
This goes back to having drives with no media present, like USB media readers.
At this point in the code, we can't yet use mediaPresent because we don't have
all the device objects set up. So, we just have to rely on partedDisk being
None. Besides, checking for None is always a good idea anyway.
|
| | |
|
| |
|
|
|
| |
Instead of only deactivating an array whose state is some variation on
"active", try to deactivate any array that appears to be assembled.
|
| | |
|
| |
|
|
|
|
| |
This modifies the behavior from commit 72d46dbe2b99c4, which was causing all
partition requests involving RAID (or probably LVM too) to get thrown out of
the auto partition requests list.
|
| | |
|
| | |
|
| |
|
|
|
| |
The one thing that has to happen when cancelling any action is that it
must be removed from the DeviceTree's list of actions.
|
| |
|
|
|
|
|
|
|
|
| |
(#497407)
This should fix traceback met when we were updating sysfs path attribute of md
device in active-idle state (empty string was returned as the device was not in
state clean or active). I think it is a state very rarely met in our tests.
According to md.txt, it is "like active, but no writes have been seen for a
while". I prepared updates.img for testing, but we can't reproduce the bug.
|
| |
|
|
|
|
|
|
| |
Since cciss device names have a subdirectory (i.e. cciss/c0d0p1) they are
represented in sysfs with a ! so that it doesn't incorrectly have an extra
subdir in the sysfs namespace. When anaconda gets the device name from sysfs
it was trying to lookup the name with a ! but anaconda stores them with the /
in the name.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
The _getExistingSize() method in class FS will using the filesystem
info/dump utility to figure out the size of the filesystem. Each
filesystem must define _infofs, _defaultInfoOptions, and
_existingSizeFields.
|
| |
|
|
|
|
|
|
| |
Noticed that ext4 filesystems were presenting users with a 'migrate to'
combo box with 'ext4' as the only entry. Tracked down the problem to
the migratable property override in Ext3FS. Changed it around to use
helper functions with property() and the UI is working more sanely now.
Users cannot select ext4 as the migration target for ext4.
|
| | |
|
| |
|
|
|
|
| |
The label "loop" in parted means devices that have no partition table but
have a filesystem. Since anaconda does not handle this state, we shall
handle said devices as if they had no label.
|
| |
|
|
|
|
| |
We need to make sure the mac partition table partition is in the device tree
before going any farther in anaconda, or we'll get a traceback when reviewing
the layout in the UI.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
Request sorting is supposed to depend on the number of disks a given
request can be allocated from (req_disks), not what disk it is currently
allocated from (parents).
|
| |
|
|
|
|
|
| |
Doing so means we eventually end up trying to bind mount /mnt/sysimage/dev
onto /mnt/sysimage/dev, which of course is never going to work. That means
there's no device nodes and we can't get the boot blocks off devices to see
if the upgrade bootloader option should even be offered.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
Resizing can introduce errors too, so for paranoia, we should
check afterwards
|
| | |
|
| |
|
|
|
|
| |
In non-kickstart installs, clearPartType gets set to CLEARPART_TYPE_LINUX
before the user makes a choice. We shouldn't pass that value to the
device tree constructor unless we're doing a kickstart install.
|
| |
|
|
|
| |
If we're not clearing any partitions, return early. Also, be more explicit
about the CLEARPART_TYPE_LINUX case.
|
