| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
|
|
|
|
|
|
|
| |
Since the newui custom spoke creates all partitions with a base
size of 1MB this check had to be moved to after allocation is
complete since the base size is nearly meaningless in the context
of these checks.
|
|
|
|
|
|
|
|
|
|
|
| |
In the case where the new partition is going to be the first logical
partition on the disk (and therefore require creation of an extended
partition) we were failing to correctly set things up to perform the
growth calculation. This led to sub-optimal placement of partitions.
This also fixes a small bug that caused us to jump to the new
candidate free region even when it offered the same growth
potential as the old/current one.
|
|
|
|
|
|
|
| |
Subvolume size is the same as the volume size. Adding a new
subvolume means growing the volume, which requires us to
update the other subvolumes' selectors' sizes to keep them
all in sync (and prevent spurious size adjustment operations).
|
| |
|
|
|
|
|
| |
This prevents automatic selection of stage2 as stage1, which is
something we never want to happen.
|
| |
|
|
|
|
|
|
|
|
| |
Instead of adding command line option throwing exception in one place
of the code, let's use SIGURS1 as signal for raising exception in anaconda.
This way, it is possible to raise exception in different phases of the
installation and we can add code to prepare worst case scenario testing
as much resolved bugs in exception handling as possible.
|
| |
|
| |
|
|
|
|
|
|
| |
The #2 and #3 dialogs already grab the correct labels so by trying to do so
again in _set_free_space_labels, we're making sure to get the wrong thing
and end up with a traceback.
|
|
|
|
|
| |
It's all because doKickstartStorage and StorageChecker.run can take a long
time, and they were being run synchronously.
|
| |
|
| |
|
|
|
|
|
| |
Also switches the reformat check to use format names instead of
types since the names are what we populate the fstype combo with.
|
| |
|
| |
|
| |
|
|
|
|
| |
Leading space isn't useful for growing a filesystem.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
With larger partitions we were starting with the default size of
500MB and growing as close as possible to the requested size, but
for smaller requests we were attempting a fixed-size allocation.
That's no good because it's a change in behavior for requests
below a somewhat arbitrary size and the difference is the smaller
(fixed) request allocations are more likely to fail. The solution
is to always use a base size of 1MB instead of 500MB. It works
without messing up partition growth because all partition sizes
get fixed after their first allocation, which means that at any
point where we're growing a request with a base size of 1MB we
know that any other growable requests will have the same base size.
|
|
|
|
| |
Also I really hate placeholders. Stop making them, glade.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
This also changes the back-signal to button-signal. This is prep work for
allowing individual spokes to relabel the button if they so choose.
|
| |
|
|
|
|
|
| |
- Splits doInstall to doInstall and doConfiguration
- Updates text and gui mode to use doConfiguration
|
|
|
|
|
|
|
| |
It doesn't make sense and can cause traceback when replacing the last
layout in the list of added layouts.
Resolves: rhbz#854643
|
|
|
|
|
| |
Instead of modifying passed iterator, iter_previous now returns a new
one.
|
|
|
|
|
|
|
|
| |
For yum payloads we write storage config before installing the payload
so %post scripts have access to the configuration files if needed. For
live installs, we have to write the config after installing the payload
since installing the payload would overwrite parts of the storage
configuration (notably /etc/fstab).
|
| |
|
|
|
|
|
|
| |
By hardcoding newlines in the source text, I made it difficult for translators
to correctly make sure their text wrapped. Instead, remove the newlines and
just have gtk figure out where the wrapping should go.
|
| |
|
|
|
|
|
|
| |
That is, when you start typing in the entry box it should filter the results in
the list instead of displaying a drop down. This also allows for typing either
the English or native names and having both work for filtering.
|
|
|
|
|
|
| |
Instead of constantly creating new Images and shoving them into a spot in
the notebook, I'm now just putting each rnote on its own page. Whether
it's better or not is up for debate, but at least this way works.
|
|
|
|
|
| |
Try to make it clear that activating the checkbutton opts out
of automatic partitioning.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
If automatic partitioning fails, we reset the storage instance to its
prior state. The custom spoke operates on a copy of the storage
instance, so that means it gets reset to whatever the state was upon
entering the custom spoke. For the storage spoke we have little choice
but to actually call self.storage.reset() which actually re-scans the
devices.
For other operations within the custom spoke, the goal is to restore
things to the state prior to the failed action. If that fails, the
custom spoke will simply reset its storage instance as described above
for automatic partitioning failures.
|
|
|
|
| |
Also remove unused PartitioningWarning exception.
|
| |
|
| |
|
|
|
|
|
| |
BTRFS default RAID level is single, so we need that to be a key in
the raid_level_features dict.
|
| |
|
|
|
|
|
|
|
| |
Using --force --force is not enough, 'lvm' still asks, if we really
want to remove PV used by some VG. Adding --yes fixes the issue.
Resolves: rhbz#853977
|
|
|
|
|
| |
Using GLib.idle_add for action that repeats means 100% CPU usage. So
let's use GLib.timeout_add with 250ms interval instead.
|
|
|
|
| |
Use desktop configuration tool.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
On F18 with Anaconda 18.6.5, adding new passphrase to LUKS format always fails:
----> 1 fmt.addPassphrase("XYZ")
/usr/lib64/python2.7/site-packages/pyanaconda/storage/formats/luks.pyc in addPassphrase(self, passphrase)
246 passphrase=self.__passphrase,
247 key_file=self._key_file,
--> 248 new_passphrase=passphrase)
249
250 def removeKeyFromFile(self, keyfile):
/usr/lib64/python2.7/site-packages/pyanaconda/storage/devicelibs/crypto.pyc in luks_add_key(device, new_passphrase, passphrase, key_file)
133
134 cs = CryptSetup(device=device, yesDialog = askyes, logFunc = dolog, passwordDialog = askpassphrase)
--> 135 rc = cs.addPassphrase(passphrase = passphrase, newPassphrase = new_passphrase)
136
137 if rc<0:
In recent cryptsetup-python-1.5.0-2.fc18, cs.addPassphrase was replaced
probably by cs.addKeyByPassphrase (I'm just guessing by the name). I tested it
just in my dummy applications, take it with a grain of salt.
Signed-off-by: Jan Safranek <jsafrane@redhat.com>
|
|
|
|
|
|
| |
We've gotten some complaints that it's not obvious what to do with the left
side of the software screen. A radio button makes it obvious that (1) you
need to pick something, and (2) you can only pick one thing at a time.
|
| |
|