| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
| |
This fixes bug #569373, where exiting the filter screen would leave the
/dev/dm-7 and /dev/dm-8 devices missing. It appears that device-mapper
is removing the devices when udevadm trigger --action=add
/class/block/dm-0 is run.
|
| |
|
|
|
|
| |
This reverts commit 8a4fdd59c1d0d613cb32778b7142da8ec0adbab1.
|
|
|
|
| |
This reverts commit a24e722ebcb06c88f88605190caebdcf83236690.
|
| |
|
|
|
|
|
|
| |
Sometimes we need to compare serials, and sometimes we need to display
them. The two aren't necessarily the same thing, so add a function to
differentiate them.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
Throughout stage2 if we bring up the network after doing various actions,
we need to make sure the DNS resolver is reset to pick up the new information.
However, pycurl/libcurl uses the c-ares resolver which does not have a
method similar to res_init. Instead we need to tear down the pycurl.Curl
object instance cached in urlgrabber and create a new one. This does the
same thing as re-reading /etc/resolv.conf, but in more steps.
|
| |
|
|
|
|
|
|
|
|
| |
Unrealizing the button box creates a mystery hidden window that causes two
problems. First, it steals the focus so keyboard controls don't work on
the filtering UI. Second, it causes a lot of gtk warnings on tty1. Instead
of unrealizing, the fix is to just hide and disallow show_all working on
it later.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This patch adds a warning when ignoring BIOS RAID members because no complete
set using them could be found.
This patch also introduces a much needed InstallInterfaceBase class, as I
didn't feel like adding the exact same code to all of cmdline.py, gui.py and
text.py .
Note that the ignoring of BIOS RAID members is checked in 2 places, as
the filter UI can be skipped under certain circumstances (kickstart). The
interface code checks for disks it has already warned about.
|
|
|
|
|
| |
rs.get_members() also returns subsets with layered raids, we only
want the devices, so filter the result of rs.get_members() .
|
| |
|
| |
|
|\ |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
This patch also moves rootPassword into Users where it belongs and auth
into Security where it belongs.
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| | |
This also removes the hack where upgrade can be True, False, or None in order
to test whether we've seen the upgrade screen or not. Instead, it introduces
a global value hack. I consider this the slightly cleaner approach.
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| | |
anaconda.ksdata is only non-None if there's a kickstart file, just like
anaconda.isKickstart would be. Therefore, we don't need two variables
to test for the same condition.
|
| | |
|
| |
| |
| |
| |
| | |
Also use short form of format type names. The long form is for
the user interface only.
|
|/ |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
(1) The filtered model is no longer the top-level so anywhere we want to call
refilter, we need to dig down and get the child, which happens to be the
filtered model.
(2) Similarly, we can only call get_text on the child of a ComboBoxEntry because
that's the entry part.
(3) Populate all search drop-downs when the containing hbox is realized, not
some complicated setup where each individual item is selected.
|
| |
|
|
|
|
|
|
| |
Since we're stuffing more things into this column than just WWIDS (paths on
iscsi and s390 stuff soon, at least) the column header needs to be changed
to match.
|
|
|
|
|
|
| |
Doing this allows use of map and filter, which seems more natural than the
iterator dance. This patch also fixes a problem drilling down to the base
store through all the various models.
|
|
|
|
|
| |
For some reason, doing it the other way around allows you to click on column
headers but there is no sorting that happens.
|
|
|
|
|
|
|
| |
For the common home/laptop use case, the user likely only has one disk. If
that's the case and they pick the Basic filtering UI (indicating they don't
want to add fcoe/iscsi/whatever disks), then there's no point in showing
these UI components.
|
|
|
|
|
|
| |
This brings iBFT (iscsi) / EDD (FCoE) / /tmp/zfcp.cfg (zfcp) auto discovered
drives only. So that they show up in the filter UI and can be selected for
the installation (tested with iBFT).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
1) When populating the store make left / right visible depend on if the
disk is listed in clearPartDisks or not
2) Don't extend clearPartDisks when moving to the next screen, but set it
so that drives which were moved to the left get removed from it.
3) The bootdisk is part of cleardisks, don't put it in
clearPartDisks twice
4) Update the bootloader drivelist, putting the select drive on the front,
don't override it. Even if we just want to mount a disk it should still
count in our bios drive order, so that grub gets a correct map
(Note even before this fix this was already effectively being done
by bootloader.py which overrides the drivelist as set by clearpart_gui)
Note this patch only fixes back/forth issues with the UI code, there is
still a problem in the underlying logic code, where after having
autopartitioned once, subsequent attemps will fail with no free space found.
I've filed this as bug 559233.
|
| |
|
|
|
|
| |
request.disks should be request.req_disks
|
|
|
|
|
|
|
|
| |
Replace all usage of the isys C EDD code with the new storage
python EDD code. Note that this moves the sorting of partition.req_disks
from devices.py to paritioning.py, because sorting now needs access
to the storage object, this also has the added advantange that now we
always allocatePartitions in sorted drive order, even in interactive mode.
|
|
|
|
|
|
|
|
| |
Since all notebook pages share the same store, a device being visible on one
page means it'll be counted as being visible on all pages. That means
flipping to the correct initial page doesn't work. Instead, we need to count
using the visible methods on callback objects to only count the devices that
are members of each page as visible.
|
|
|
|
| |
Previous version had a missing break. Put the break in.
|
| |
|
|
|
|
|
|
| |
This makes the way they are displayed in the filter UI and in
cleardisks_gui.py consistent, and this makes us not show dmraid device
node names for sets which we will later activate with mdraid.
|
|
|
|
|
| |
Now that MD BIOS RAID arrays have their own type, there is no longer a
need for the biosraid property.
|