| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
a real Python package.
Also updates the build and autotools stuff to work with the new structure
|
| |
|
|
|
|
| |
Editing extended partitions and setting mountpoints and the like for
them is not a good idea. The only useful edit of extended partitions
would be resizing of pre-existing ones and we don't support that.
|
| |
|
|
|
|
|
| |
Resolves: rhbz#592185
Display a message to the user when the mountpoint name they have
chosen is invalid. Skip checking when the format type has no mountpoint.
|
| |
|
|
|
|
|
| |
Resolves: rhbz#592185
Display a message to the user when the mountpoint name they have
chosen is invalid. Skip checking when the format type has no mountpoint.
|
| |
|
|
|
|
|
| |
Resolves: rhbz#592185
Display a message to the user when the mountpoint name they have
chosen is invalid. Skip checking when the format type has no mountpoint.
|
| | |
|
| |
|
|
|
| |
Disks that are components of a biosraid array or multipath device will
not be displayed.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
I know Hans wants to remove the screen, but let's just make it less
annoying until then.
|
| |
|
|
| |
originally removed in 2008 by 7ad65d9e30fd21d8c0356dc998ea97c579a73d53.
|
| |
|
|
|
|
|
|
| |
Before, we were just having ayum.searchNevra return a list of packages and grab
whatever happened to be first on that list. Sometimes it ends up being the
x86-64 package, and sometimes it ends up being the i686 one instead. To be
more deterministic, we should return the best package for the architecture
we're running on always.
|
| |
|
|
|
| |
We need to make sure the config file is there every time, or else
/sbin/multipath helpfully does nothing useful at all.
|
| |
|
|
| |
Related: rhbz#560666
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Key patch of series. enableNetwork method is the root of all other
changes in the patchset. The method is used both for network enabling
in stage 2 triggered by need of network (repos, network storage, etc..)
and [Configure Network] button
What we select in stage 2 network UI is:
- device to be activated (only in case of network enabling), this is
controlled by ONBOOT ifcfg setting, note that devices actually
activated depend on editing in nm-c-e
- devices to be controlled by NM (and thus visible in nm-c-e),
this is set by NM_CONTROLLED ifcfg setting
A dialog for that is part of the patch, it needs some polishing.
bringUp method had to be split into write and waitForConnection
because in case of just config, without actually activating any
device in nm-c-e, we don't want to wait for activation.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Remove reading of some keys from NM via dbus, count on ifcfg
file contents (written by stage 1, ks, or nm-c-e). This should
also ensure support for ipv6 in stage2 using nm-c-e.
Remove available() method - it is useless - HWADDR is read from ifcfg
file, description is set in constructor, and Network class will be
kept up-to-date (e.g. after configuring with nm-c-e) by explicit
call to added update() method.
readIfcfgContets became useless, we can use (now ifcfg-backed)
NetworkDevices' method loadIfcfgFile instead.
Hunk starting with if len(available_devices) > 0: is a noop,
probably some leftover - removing.
|
| |
|
|
|
| |
Note: other occurences of 'DESC' usage are replaced in following
patches.
|
| |
|
|
|
|
|
|
|
| |
it has been virtually nonexistent for three years, see
9e1a444c46abcfc29c2e44ffd102fcc1eda6289e,
2d90bc12dcc682a7f0ff68e599cbb81a34a0b4a3 and
076c853f50c10203b45a552735f692b13a191bcb.
I found out about this when auditing the rawhide logs today.
|
| |
|
|
| |
Related: rhbz#560666
|
| |
|
|
|
|
|
|
|
|
| |
Remove the raid clone option from the create-storage menu, and also
remove the underlying code. It is broken, and this has not been noticed
until very recently as no-one uses it. So as discussed on irc it is better
to just remove it, otherwise the next time we accidentally break it,
it will likely once more remain broken for a long time.
This also "fixes" RHEL-6 bug 589957.
|
| |
|
|
|
|
|
|
|
|
| |
In the Edit Partition dialog, disable Resize if Format is checked and
disable Format if Resize is checked. Users cannot check both Format and
Resize and have it perform a useful operation. Technically, it's
possible, but our UI workflow in anaconda does not really allow an easy
way to accomplish this. For now, prevent users from selecting both
Format and Resize. If we want to let people shrink a filesystem and
reformat it, we can get creative with that later.
|
| | |
|
| |
|
|
|
|
|
|
| |
The problem here was that ClearDisksWindow._remove_clicked wasn't even getting
called on double click. Instead, DeviceSelector._row_activated was getting
called because it was the first registered signal handler in the chain. Adding
a second handler appends to the chain. It does not remove previously added
handlers.
|
| |
|
|
|
| |
We want to have a sane default for the UTC checkbox so we need to
fixup hasWindows() rather then removing it.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
As pylint rightfully points out the hasWindows function from bootloader.py
is broken, it tries to access bootloaderInfo.dosFilesystems, but
bootloaderInfo refers to the bootloaderInfo class, not the module.
This does not cause any tracebacks because it tries to access
bootloaderInfo.dosFilesystems while iterating over bootloader.images, and
bootloader.images has not been set up at this time (so its an empty dict).
Thus hasWindows() will always return false, as there is no way to
determine hasWindows at this point during the installation (we have not yet
paritioned, so any exsting windows partitions may end up being removed),
this patches fixes things by simply removing the hasWindows function and
fixing up any callers of it.
|
| |
|
|
|
|
|
| |
This has a tricky part: the checkbox toggle callback in our implementation
(WideCheckList.toggled_item) is called *before* the actual toggle
occurs. This has to be considered in the button-enabling code. An
alternative would be to change/extend the toggle callback hook mechanism.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
On s390, if you had a single DASD that needed dasdfmt run, you would get
a ZeroDivisionError traceback because the self._totalCylinders value was
zero. The problem was caused by the DASD.totalCylinders property and
how it initialized. It would initialize itself on the first call, but
since we'd already fired off a dasdfmt process for the device, the one
running to capture the cylinder count couldn't get access to the device.
Users with more than one DASD needing a dasdfmt would not see the
traceback, but would have an incorrect total cylinder count, so 100%
would be reached when n-1 devices had been formatted.
Honor the exclusiveDisks list in the storage object and log the
/dev/disk/by-path alias for the device when logging the info message
about what device was found that was unformatted.
[Originally worked up in November 2009, I've updated the patch a bit to
work with our current code. Tested in text mode and gui mode. If you
have any unformatted DASD devices, anaconda prompts you and asks if you
want to format them.]
|
| |
|
|
|
| |
The purpose is to select which device gets the bootloader installed, not
which device contains /boot.
|
| |
|
|
|
|
|
|
| |
lv.format.currentSize remains on the original value all the time. This
means that when the user resizes the LV once, currentSize stays the same
and the test for change in lvm_dialog_gui.py always succeeds every time
the user reopens the LV edit dialog. This causes a traceback just below,
in ActionResizeFormat.
|
| |
|
|
|
|
|
| |
We unset storage.clearPartType so that all devices will be found during
reset of storage, but we need to restore it afterwards since the user
is headed to the cleardisks screen and not necessarily all the way back
to the parttype screen where clearPartType would get set again.
|
| |
|
|
| |
Resolves: rhbz#582660
|
| |
|
|
| |
Resolves: rhbz#582676
|
| |
|
|
|
|
| |
I introduced the immutable column in DeviceSelector without making space for
it in the cleardisks store. So, add a new column to the store and make all
values in it False to indicate nothing's immutable.
|
| |
|
|
|
| |
Courtesey of pylint, this patch also fixes some things which are not
syntax errors but still make pylint unhappy.
|
| |
|
|
|
|
| |
In the storage filtering UI, we need to call the startup() method of
storage.dasd.DASD so it will check for unformatted DASD devices and
offer the user the ability to format them.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
commit 8e62952a0e52d9ac5df781eb2f4ff5915208602b causes a number of
issues for biosraid / mpath:
1) For biosraid it passes the raidset name to _active, but _active
expects a udev info dict now
2) _active now takes the name to compare to exclusivedisks from the passed
udev info dict, but for biosraid and mpath the name stored in exclusiveDisks
is not the member udev name, but the name of the higher level device
(Note the code before the above commit already got this wrong for the
mpath case)
This patch fixes this by:
1) Passing the fake udev info data for biosraid sets to _active and
to _isProtected (it adds a sysfs_path entry to the fake data for this).
This fixes both above problems for biosraid
2) Creating fake udev info data for mpath, setting the name of that
to the name of the higher level device and using that as _Active
and _isProtected argument. By also storing this info dict into to
store, we can can also drop the special mpath case in getNext()
|
| | |
|
| | |
|
| |
|
|
| |
You know, like anaconda's any other python module.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Network has to be enabled before setting the repo up so that repo metadata can
be checked (http/ftp case) or even before nfs filesystem is mounted (nfs case).
The bug is regarding the cases where network has not been anabled yet and user
is adding network-requiring repo, or modifying non-net-requiring repo to a
requiring one (e.g. DVD install -> http install).
It can be worked around (apart from restarting install with ks, or something
that would bring up network earlier) by canceling the dialog, and checking or
modifying existing (*if there is any*) network requiring repo which would bring
up network enablement dialog.
|
| |
|
|
|
|
|
| |
We don't want people to be able to deselect these devices, but we still want to
show them. Not showing them leads to a variety of annoying hacks and has the
unpleasant side effect of having previously hidden devices suddenly show up in
later UI screens.
|
| |
|
|
| |
Adds 'originalFormat' to lv dict, missing from fcd6820064d.
|
| | |
|