| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
| |
This is a preparation patch for adding support for writing
the necessary dracut cmndline options to grub.conf
|
| |
|
|
|
|
| |
This can be helpful in determining the cause of failed upgrade from log.
I used it when working on #499321. Can be kind of corner-case, but can't
hurt.
|
| | |
|
| | |
|
| |
|
|
|
| |
We have lots of strings that we display to users which are unclear or
contain poor usage and grammar. That's bad.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This patch adds support for using FCoE during the installation. This patch
merely lays the initial ground work, there is more work todo:
- The system will not boot without manual help after the install, as
dracut / mkinitrd do not support FCoE yet
- If FCoE is not used for / but for example for /srv, then information
about the nic used for FCoE needs to be written in a to be defined
config file in the system, and rc.sysinit needs to be thought to read
this file and bring up FCoE SAN's / Fabrics not used for /
- kickstart support for FCoE still needs to be done
|
| |
|
|
|
|
|
| |
Fix of this UI flow: doing storage reset after root partitions discovery (e.g.
in partitioning step) and then going back and selecting upgrade. In place of
using root partition device objects obsoleted by storage reset, find root
partition devices of new device tree.
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
In storage.Storage we keep the device specifications as provided to us.
In the devicetree, during population, we use udev to resolve the user-
provided specs to device names. As we create StorageDevice instances for
the devices, we set a new attribute ("protected") as appropriate. Once
the DeviceTree is populated, we use the devices' protected attribute to
determine whether or not they contain installation media. This way we
can track protected devices even when their names change.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
(#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.
|
| |
|
|
|
| |
When calling udev_trigger for the save exception to local storage
device, limit the call to block devices.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
| |
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 the line contains a filesystem we do not recognize or a device that
we are unable to resolve we will just write it back out as-is if/when
we write out a new fstab.
|
| |
|
|
| |
This is just a clean-up for consistency.
|
| | |
|
| |
|
|
|
|
|
| |
This parameter basically means a protected partition cannot be modified or
deleted, but can be dealt with on a read-only basis. Right now, the only
time we need that is so the hdiso install source can be written out to
/etc/fstab.
|
| |
|
|
|
|
| |
Remove the chunk of code that sortds bind mounts to the end. It appears
to be completely bogus, and certainly breaks mounting of /dev during
installation.
|
| |
|
|
|
|
| |
If available, use device.format.mountType instead of device.format.type
when writing out fstab. This way we write out the real fstype name, not
the UI name.
|
| |
|
|
|
|
| |
We have to try as late as possible to identify the device that contains
the swap file to maximize the chances that the filesystem will be
mounted when we go to look for it.
|
| |
|
|
|
| |
For swap files we need to know anaconda.rootPath and since we're also
using anaconda.intf it seems like time to just give in and pass anaconda.
|
| |
|
|
| |
This fixes a traceback during upgrade mount.
|
| | |
|
| |
|
|
|
| |
This adds the newly established passphrase to all preexisting LUKS
devices so that the system can be booted by entering a single passphrase.
|
| |
|
|
|
|
|
|
| |
When we're parsing /etc/fstab the directories that serve as the devices
in bind mounts are not going to be present, so we will have a hell of a
time figuring out what devices contain them. However, in
FSSet.mountFilesystems we should have those dirs set up already, making
it possible to sort out.
|
| |
|
|
|
| |
Enforce that certain mountpoints must be on a native Linux filesystem, and
that certain directories must not be on their own filesystems.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
When a PV partition is part of an inconsistent VG, and the user chooses
to ignore it we currently remove it from the devicetree, but since
partition_gui.py populate() uses parted on the disk to find out about
the partitions, it will still see it and then backtrace when it cannot
find it in the devicetree.
This patch fixes this by instead making the partition immutable. Note
that I've put the reason for it being immutable in the new immutableDevices
array, so that if we have similar cases in the future we can use
immutableDevices for that too. We might even want to move some of our
existing cases there.
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Layout editation (#495848)
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
