Description of problem:
Clicking Reset All in Blivet partitioning makes anaconda crash.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. have some existing installation on disk (in my case, Fedora Workstation default layout)
2. boot anaconda, go to blivet partitioning
3. perform some change, e.g. reformat /boot
4. click Reset All, confirm
Created attachment 1985070 [details]
bug video demonstration
Created attachment 1985071 [details]
Created attachment 1985072 [details]
Created attachment 1985073 [details]
Created attachment 1985074 [details]
Created attachment 1985075 [details]
Created attachment 1985076 [details]
Created attachment 1985077 [details]
Created attachment 1985078 [details]
Proposing as an F39 blocker
The same crash happens in Workstation, this is not limited just to netinst, likely a universal issue. For some reason, the coredump wasn't present in coredumpctl in GNOME, and abrt didn't pick it up. But it's in coredumpctl in netinst - if needed, I can try to gather a proper stack trace. But this should be trivial to reproduce by developers, I think, so I didn't do that right away.
Kamil, how you have reproduced this on the Fedora-Workstation-Live-x86_64-39-20230824.n.0.iso? Since in this iso it opens the webUI interface and blivet gui looks a bit different from the video you posted.
Created attachment 1985185 [details]
Screencast - cannot reproduce the bug
I tried to reproduce the bug usign the blivet interface offered by webUI, and its different from what Kamil found.
(In reply to Geraldo Simião from comment #12)
> Kamil, how you have reproduced this on the
Sorry, I didn't realize that my statement was confusing. I tested this with the 20230823 workstation iso, which still has the GTK anaconda by default. In that situation, that crash occurred as well. I haven't tested the webUI interface.
This is accepted as Beta FE and Final blocker for now, vote on Beta blocker status is unclear. https://pagure.io/fedora-qa/blocker-review/issue/1189
Discussed during the 2023-08-28 blocker review meeting: 
The decision to classify this bug as a "RejectedBlocker (Beta)" was made as we agree that this doesn't quite violate the Beta criteria. Note it is already accepted as Beta FE and Final blocker.
updates image for Fedora 38: https://vtrefny.fedorapeople.org/img/rhbz2234466.img
upstream PR: https://github.com/storaged-project/blivet-gui/pull/405
Created attachment 1986135 [details]
journal with updates.img
I applied the updates.img (I think! When I grep journal for "rhbz", it seems to suggest it was applied, but I don't see /tmp/updates.img created, as it used to be in the past), but I still see the same crash, using the same reproduction steps as in comment 0. Journal attached.
For the record, I used Fedora-Everything-netinst-x86_64-39-20230824.n.0.iso and the updates.img on top of that.
FEDORA-2023-5600f2c280 has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2023-5600f2c280
(In reply to Kamil Páral from comment #19)
> For the record, I used Fedora-Everything-netinst-x86_64-39-20230824.n.0.iso
> and the updates.img on top of that.
The updates image works only with Fedora 38 and Python 3.11, Fedora 39 already has Python 3.12 so the updates image doesn't work there.
updates image for F39: https://vtrefny.fedorapeople.org/img/rhbz2234466_f39.img (tested with Fedora-Everything-netinst-x86_64-39-20230829.n.0.iso)
Thanks. Both the F39 updates.img and the submitted update work OK for me.
FEDORA-2023-5600f2c280 has been pushed to the Fedora 39 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-5600f2c280`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-5600f2c280
See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-5600f2c280 has been pushed to the Fedora 39 stable repository.
If problem still persists, please make note of it in this bug report.