| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Instead of crashing, inform users they should use integer values when
entering partition sizes.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Cases I tested:
(spoke is pre-hub network spoke)
Link has (slow) dhcp:
- connected in payload init, connected in spoke
- not connected in payload init, connected in spoke
- fixed by the patch
- not connected in payload init, not connected in spoke
- subcases: - wait for connection in spoke
- leave spoke while connecting
- fixed by the patch
Link does not have dhcp:
- configure static connection and leave spoke
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
There are three problems with the current resize action UI:
(1) You can't discover that there's a drop down in the action column because
there's no down arrow. GTK simply doesn't do that.
(2) We can't filter out shrink from the drop down on a per-filesystem basis
without layering on all the usual filter store crud.
(3) Something about interacting with a GtkCellRendererCombo causes the layering
of dialogs to get screwed up such that coming back to the storage spoke after
visiting the resize dialog appears locked up, because the dialog is displayed
under the spoke.
This commit fixes all these problems by getting rid of the drop downs in the
action column and adding a communal set of tool buttons for setting the action
you want.
|
|
|
|
|
| |
Live environments have their own way of rebooting, and anaconda doesn't need
to interfere with that.
|
| |
|
|
|
|
|
| |
You do this by simply highlighting the currently selected boot device and
clicking the Boot Device button again.
|
| |
|
|
|
|
| |
Related: rhbz#877871
|
|
|
|
|
|
| |
Our current plan for handling of incomplete preexisting LVM does not
involve filtering out or ignoring anything, so this is a good first
step.
|
| |
|
|
|
|
|
|
|
|
|
| |
The obvious example is a VG with no LVs, which could happen because it
actually has no LVs or because only some of its encrypted PVs have been
unlocked.
This may end up being how we handle degraded md and incomplete lvm in
the future.
|
|
|
|
|
| |
Fix the TypeError problem with iutil.execWithCapture() when fatal
and process returns a non-zero exit code.
|
|
|
|
| |
This is so we can test this from unit tests running as non-root.
|
|
|
|
|
| |
Re-arranges a bit of code and handles dracut mounted hd isos.
Also handles a None type on self._currentIsoFile better.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The case:
1) Dracut does not use network so it does not write any ifcfg file
(e.g. DVD install)
2) NM creates default auto connection (DHCP) because it can't find
any ifcfg file for a device.
3) Anaconda writes out default ifcfg file (e.g. ifcfg-eth0)
4) When editing a connection in nm-c-e, ifcfg file of edited default
auto connection (Wired connection 1) is created
(ifcfg-Wired_connection_1).
5) If anaconda tweaks any ifcfg file later (setting ONBOOT, NM_CONTROLLED),
it is the ifcfg-eth0.
6) Both ifcfg files are copied to the target system at the end of
installation
Luckily, the ifcfg-Wired_connection_1 seems to be used after installation,
but bug #870922 suggests it might be not so in all cases.
Anyway, we shouldn't create anaconda's ifcfg-ethX default file in this case.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
These may not fix anything we've got right now, but it's the more correct
way to do it.
|
|
|
|
| |
We're not going to have this done in time for F18 anyway.
|
|
|
|
|
|
|
|
| |
This time it shoves all the logging data into packaging.log
This commit has some hacks to work around yum issues. I've discussed
with upstream and they're going to work on better APIs around logging in
the future.
|
|
|
|
|
|
|
|
|
| |
We could have method of nfs:server:/path/ or nfs:server:/path/foo.iso.
Dracut could have left stuff mounted to /run/install/repo or
/run/install/isodir or both. In any case we should detect what's been
left over and setup yum the right way.
This introduces a couple new constants as well.
|
|
|
|
|
|
|
|
|
| |
Fix translation from AUTOPART_TYPE_BTRFS to DEVICE_TYPE_BTRFS so
we create new devices as btrfs instead of md when btrfs is the
default.
Also close gaps in raid feature selection ui and add checks to
save_right_side to prevent some invalid raid setups.
|
| |
|
|
|
|
|
|
| |
The keyboard layout testing text box had no padding and any text you
typed in it looked weird. This patch adds a 6 px border around the
inside to give it some padding.
|
|
|
|
|
| |
Otherwise, previously unselected disks on the storage overview will never
be allowed to be selected.
|
| |
|
| |
|
|
|
|
|
| |
This is not handled by similar code in the software spoke, because that code
is never run for kickstart installs containing a %packages section.
|
|
|
|
|
|
|
| |
This does the same sort of stuff the previous storage patch did, but for
the custom partitioning screen. It takes the grid that was outside of
the alignment and moves it inside, and also resets the xscale/yscale on
the alignment to 1,1, and sets some of the expand stuff.
|
|
|
|
|
|
|
|
|
|
|
|
| |
The glade changes here move the grid3 widget into the main alignment
widget in the storage.glade file; previously the grid3 alignment was
adjacent to the alignment widget. When grid3 was outside of the
alignment, there was a consistent and noticeable upper-left-corner =>
lower-right-corner growth motion visible when first entering the spoke.
After putting grid3 inside the alignment, the screen loads up in one go
without any growing or shifting beforehand. Various expand settings and
scale settings on container widgets from the alignment down were also
tweaked.
|
|
|
|
|
| |
There is an entry for filtering, searching doesn't work (it probably
uses the underlaying non-sorted model) as it not needed.
|
|
|
|
|
|
|
|
| |
Emitting signals from the function that handles other signals is dangerous
given the synchronous nature of GTK signals, so this was never a good idea
to start with. Then, displaying the dialog from the main loop means it
gets displayed in the lightbox correctly instead of over a completely grey
background.
|
|
|
|
|
|
| |
This removes code duplicated in desktop.py, and will short circuit the
routine if the user has indicated that they want a graphical boot by way
of kickstart data.
|
| |
|
| |
|
|
|
|
| |
Get rid of unused import, use super(), remove some spaces
|
|
|
|
|
|
| |
This uses the new constant to link to the right target by name. It also
removes any fiddling with /etc/inittab as we don't want/need to touch
that any more.
|
| |
|
|
|
|
| |
We don't provide you with the chance to do anything anyway.
|
|
|
|
|
|
| |
We are trying to prevent the user from getting to the hub with a space
error, hence why you can only quit. It's still helpful to catch the
errors just in case something sneaks through later.
|
| |
|
|
|
|
| |
Related: rhbz#872833
|
|
|
|
| |
The logic for handling it implicitly only works for partitions.
|
|
|
|
|
|
|
|
|
|
|
| |
I don't especially want to do this, but as stated elsewhere changing language
during installation is not at all easy. It's especially not easy from this
spoke, where everything's already been imported.
Eventually I think this spoke should allow for picking which languages you
want supported on the finished system (sort of a language-specific package
selection screen), but there's no time and this will at least prevent people
from hitting a really annoying bug.
|
| |
|
|
|
|
|
|
| |
We don't use unicode strings (as a type) in anaconda.
XklWrapperr.switch_to_show_str should thus use encode("utf-8")
and also contain byte strings.
|