| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
This patch contains the following small fixes:
- There is no need to convert None as username/pass into an empty string
pylibiscsi will happily take either
- Only set the initiator name from ibft if the ibft flag is present
- Show an error when no username is specified, but a password /
reverse username / pass is given
- Do not backtrace when the following happens:
1) Manually add iscsi disk
2) enter wrong IP / username without pass
3) Fix this *and* change the initiator name initially choosen
- Allow having only a reverse password without a reverse username
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
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.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
We need to pass the mountpoint and the chroot in separately so everything
doesn't end up under /mnt/sysimage. Doing that results in the contexts
being set to mnt_t, which causes all sorts of problems on reboot.
|
| |
|
|
|
|
|
| |
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 the device contains a valid partition table we do not care what else
udev tells us is there.
Once we move to optionally partitioned devices, this may no longer be
adequate logic for this type of problem.
|
| | |
|
| |
|
|
|
|
|
| |
If you have an existing disk layout and choose custom partitioning and
want to resize an existing logical volume and filesystem, targetSize was
getting the new size value before an ActionFormatResize() was created
for the device, which resulted in a traceback.
|
| |
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
| |
In order to include these in pycryptsetup we had to create yet
another duplicate copy of execWithRedirect. This patch brings them
back into anaconda so we can easily modify them if needed until
the day when pycryptsetup has this functionality. It also allows us
to redirect the output to someplace useful for debugging.
|
| | |
|
| |
|
|
| |
This just prevents us from trying to use self.partType if it is None.
|
| |
|
|
|
|
|
|
| |
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.
|
| | |
|
| | |
|
