Description of problem:
I wanted to create a new partition in Blivet partitioning screen. I selected BIOS Boot partition type, but then changed the value of the field to btrfs. Then anaconda crashed.
Version-Release number of selected component:
The following was filed automatically by anaconda:
anaconda 33.25.2 exception report
Traceback (most recent call first):
File "/usr/lib/python3.9/site-packages/blivetgui/dialogs/size_chooser.py", line 145, in min_size_limit
raise ValueError("Size limit for minimal size cannot be greater than current maximum size.")
File "/usr/lib/python3.9/site-packages/blivetgui/dialogs/add_dialog.py", line 816, in on_filesystems_combo_changed
self.size_area.min_size_limit = self._get_min_size_limit()
ValueError: Size limit for minimal size cannot be greater than current maximum size.
cmdline: /usr/bin/python3 /sbin/anaconda
cmdline_file: BOOT_IMAGE=vmlinuz initrd=initrd.img inst.stage2=hd:LABEL=Fedora-E-dvd-x86_64-33 quiet
hawkey.log: INFO Sep-22 13:07:57 === Started libdnf-0.48.0 ===
release: Fedora release 33 (Thirty Three)
Created attachment 1715704 [details]
Created attachment 1715705 [details]
Created attachment 1715706 [details]
Created attachment 1715707 [details]
Created attachment 1715708 [details]
Created attachment 1715709 [details]
Created attachment 1715710 [details]
Created attachment 1715711 [details]
Created attachment 1715712 [details]
Created attachment 1715713 [details]
Created attachment 1715714 [details]
Created attachment 1715715 [details]
Created attachment 1715716 [details]
I can easily reproduce this even with latest Fedora-Everything-netinst-x86_64-33-20200921.n.0.iso:
1. Enter Blivet
2. Click Add partition (you need to have space - start with an empty disk or delete all partitions)
3. Select BIOS boot
4. Select btrfs or ext4 (or probably anything else)
Created attachment 1715718 [details]
bug demonstration video
Proposing as a Beta or a Final blocker:
"When using both the installer-native and the blivet-gui-based custom partitioning flow, the installer must be able to:
Create mount points backed by ext4 partitions, LVM volumes or btrfs volumes, or software RAID arrays at RAID levels 0, 1 and 5 containing ext4 partitions"
"The installer must be able to create and install to any workable partition layout using any file system and/or container format combination offered in a default installer configuration. "
The installer *is* probably able to create a workable layout, but you must avoid very trivial actions like changing target filesystem values too much, otherwise it crashes. IOW, you're stepping on a mine field.
I tried to find more ways to trigger this and I didn't. The workaround seems to be: "If you selected BIOS Boot as the partition format and you want to select a different value, cancel the dialog and open it again, then select the new value. Otherwise the installer will crash (when the field is changed to BIOS Boot to something different)."
Accepted as a Beta freeze exception and a Final blocker:
But it's still proposed as a Beta blocker, and with our current system we can't really mark that in Bugzilla, so I'll leave both blockers in the proposed state, until the Beta blocker vote is resolved.
*** Bug 1870046 has been marked as a duplicate of this bug. ***
usptream PR: https://github.com/storaged-project/blivet-gui/pull/239
updates image: https://vtrefny.fedorapeople.org/img/rhbz1881472.img
(In reply to Vojtech Trefny from comment #20)
> updates image: https://vtrefny.fedorapeople.org/img/rhbz1881472.img
It seems to fix this actual issue, but introduces bug 1881932
(In reply to Kamil Páral from comment #21)
> (In reply to Vojtech Trefny from comment #20)
> > updates image: https://vtrefny.fedorapeople.org/img/rhbz1881472.img
> It seems to fix this actual issue, but introduces bug 1881932
That one is already tracked here https://bugzilla.redhat.com/show_bug.cgi?id=1881932 The updates image contains latest version of blivet-gui (which is currently in testing for F33) + the patch so the change that broke the resize is also in it.
Rejected as a Beta blocker, so setting as accepted for Final:
FEDORA-2020-f9ad33acdd has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2020-f9ad33acdd
(In reply to Fedora Update System from comment #24)
> FEDORA-2020-f9ad33acdd has been submitted as an update to Fedora 33.
Fixes the bug.
FEDORA-2020-f9ad33acdd has been pushed to the Fedora 33 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-f9ad33acdd`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-f9ad33acdd
See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-f9ad33acdd has been pushed to the Fedora 33 stable repository.
If problem still persists, please make note of it in this bug report.