| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
| |
Required for getlangnames.py
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
We were previously using tests that have diverged from what's going on in
yuminstall.py, so this brings the two backend tests into using the same
concept.
|
|
|
|
|
|
| |
For the rhel6-branch, we now have an x.y.z version number since it was
branched from f12-branch. The bumpver target needs to handle the extra
.z component.
|
| |
|
|
|
|
|
| |
Also rewrite getNextPartitionType for clarity so that bugs like this
will be easier to identify and fix in the future.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
On s390x, linuxrc.s390 brings up the network completely and
writes an NM compliant /etc/sysconfig/network-scripts/ifcfg-<DEVICE>.
Apparently, loader never hits STEP_IP or writeEnabledNetworkInfo().
The latter would convert LAYER2= and PORTNO= into OPTIONS="".
Since it does not seem to be called, linuxrc.s390 now writes OPTIONS="".
Fixed readIfcfgContents() to not swallow OPTIONS which contains '='.
With this in place, network.py writes a correct ifcfg to /mnt/sysimage.
This patch completes ifcfg production on s390x of the following commits:
25f58fe7c701c453d39d2a9c5c0850eefce07f76
9249e40f42ffbbdcf42cd1caad72e3d622c7a75b
5f0fcf6688d08f83826c2892bb9fc97d6b4d7dd0
81163960a6137d39a5f2082e9f8d9f0a7b2ada57
This patch is intended for both devel and F-12.
|
|
|
|
|
| |
Just like we want things to not be mounted and lvm to be not active when
doing liveinstalls, we also want to start with any mdraid arrays deactivated.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
The DASD kernel parameters will be coming from DASDDevice objects.
|
|
|
|
|
|
| |
If we just iterate over the task list selecting and deselecting groups,
then we'll deselect groups we want if a later task also contains those
groups. So deselect all unchecked tasks, then select all checked tasks.
|
|
|
|
|
|
|
| |
it (#506073).
Just update the order of drives instead of using only drives entered in
--driveorder option.
|
|
|
|
|
| |
multipath and multipathd expect the leading "3" in wwids, but that's bad
in the user interface. So use one for one and the other for the other.
|
|
|
|
|
|
|
|
|
|
| |
With present UI, edit repos, not base repos (methodstr). Works with
assumption that base repo (repo/method) url points to a single repo, which is
true for Fedora (as opposed to RHEL5 where we various repos in directories).
dgregor told me that the target for RHEL6 is to have just one repo and handle
product differentiation by comps. If we had to work with multirepo base
urls, the UI for repo editing would need to be redesigned and rewritten because
now we are mixing base urls with repo urls there.
|
|
|
|
| |
We need to pass dummy repo object. Also pass methodstr as argument.
|
|
|
|
|
| |
We need it for repo editing or correction of repo= arguments in UI, especially
in case of nfs: or cdrom: which can't be stored in AnacondaYum.baseurl.
|
|
|
|
|
| |
I'd set insensitive also the other elements instead of hiding them which makes
the dialog desert. The dialog probably needs some more polishing.
|
| |
|
| |
|
|
|
|
|
|
| |
Live images don't contain volume_key, which makes sense since key
escrow is kickstart-only functionality. At any rate, failure to
import volume_key should only break key escrow.
|
|
|
|
|
|
| |
This writes a multipathd.conf that whitelists the devices we're using in
our multipath devices. It's a fairly basic configuration, and it doesn't
handle ALUA yet.
|
|
|
|
| |
This should have been part of the previous commit but wasn't.
|
|
|
|
|
| |
MultipathDevice needs its own .updateSysfsPath(), because self.name is
"mpath0" but the sysfs directory is /sys/class/block/dm-0 .
|
|
|
|
|
|
| |
(#524417).
Concerns cases when stage2= can't be parsed as http or ftp url.
|
|
|
|
|
|
|
|
|
|
| |
This patch fixes 2 issues with the parsing of the optional portnr in
iscsi target IP's:
1) We don't want to include the : in the portno, so port = target[idx:]
should be port = target[idx+1:]
2) An IPV6 IP always includes the : character, so specifying the port
was mandatory with IPV6, this patch looks for "]:" inside the
string to determine if a port is present for IPV6 strings.
|
| |
|
|
|
|
|
|
| |
If we are editing, not creating, we overwite several attributes
instead of creating a new device/action pair. Since these changes
have no corresponding action they need to be reversed manually.
|
| |
|
| |
|
|
|
|
|
| |
I hit it in the last build that I've done where the filtering was introduced
(and I have to add that I also acked the original patch).
|
|
|
|
|
|
|
|
|
|
| |
With a kickstart install, with "clearpart --label", we will end up
scanning pre-existing partitions after clearing the label. This leads
to the backtrace as seen in #527785 and #526517.
addUdevPartitionDevice() has special handling for this case, instead of
copy and pasting this, this patch modifies addUdevPartitionDevice() so
that it can be used for dmraid and multipath partitions too.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The playing around with partedPartition flags only allows us to determine
the partition table entry for certain usuages which are deemed special
by parted. For normal FS usuage, parted will default to the type for the FS
it has detected (for pre-existing partitions) or to Linux (83) for new
partitions.
This means that for example reformatting a vfat partition as ext3, or a new
partition as vfat will lead to incorrect partition type entries in the
partition table. This patch fixes this.
This patch is intended for both master and F-12.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We were resetting the parted flags for re-use of existing partitions in
destroyFormat, but this assumes that the existing partition actually has
a type in the partition table matching its current formatting, this has 2
problems:
1: If the partition has a type which needs to have flags reset to become
the correct type for the new format (for example swap -> ext2), but it
is not formatted, the flags wont get reset
2: If the partition has a type which does not match the formatting (for
example type linux raid, formatting ext2), the flags won't get reset
This patch moves the resetting of the flags to the creation of the new
format, and resets all flags except for the one for the to be created
format (and boot and lba which are special).
For the F-12 branch this also has the benefit that the resetting of the flags
happens at all, as there the resetting was happening on a deep copy of the
device (and thus the label) and never actually got written to the disk.
|
|
|
|
|
|
|
| |
It used to be so, because for boot device target (/dev/mdX) we installed into
MBRs anyway. With Hans's patch 45a7048e5f56316e052e4699b5ec70aa291ddd5e we do
what we promise (install to boot device) in this case, but it is a change and
it doesn't seem to be expected as default by users.
|
| |
|
| |
|