When trying to create a custom partition layout using the link to Blivet-GUI, I click on the Confirm button in Blivet and the operation is correctly performed, however no information is passed onto Anaconda about the new state of partitions and when I click on Next in WebUI and I want to start assigning the mount points, I am presented with the old partition layout Anaconda had discovered in the beginning. I cannot proceed until I click on "Search again" again. This is not very convenient, because I expect that the new layout will be presented both to Anaconda WebUI and me, or that I will be told about the necessity of re-searching. Reproducible: Always Steps to Reproduce: 1. Click on Modify Storage. 2. Use Blivet-GUI to create some useful layout. 3. Click Confirm and close Blivet-GUI. 4. Return to WebUI and click Mount point assignment and Next. 5. Bump - you will just see the old layout options. Workaround - Click "Search again" and then proceed as described in step 5 -> all is well in the Wonderland. Actual Results: Blivet-GUI does not trigger update of the layout for Anaconda. Expected Results: When blivet-gui is used and the new layout is confirmed and created it should update itself in the background, so that new partitions are immediately usable.
Yes, we are not able to get information that the partitioning has changed right now. For that reason we will add a dialog before running blivet with instructions how this works. I think this bug should be fix by that change.
*** Bug 2236025 has been marked as a duplicate of this bug. ***
Proposed as a Freeze Exception for 39-beta by Fedora user lnie using the blocker tracking app because: Propose this as a FE,as it's quite annoying and bring poor user experience,besides,it seems have lots of side effects: #2236356,#2236409,etc
hey, I've got a great idea - instead of launching a separate application, we could...somehow *embed* that "advanced custom" partitioning application into the installer flow? that way, the installer would know when it had finished! (please read this comment with your sarcasm detector running :>)
+4 in https://pagure.io/fedora-qa/blocker-review/issue/1247 , marking accepted FE.
I think we can say this PR addresses the main issue: https://github.com/rhinstaller/anaconda/pull/5113
FEDORA-2023-755dc0b0c0 has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2023-755dc0b0c0
So now there's a dialog shown telling you to rescan storage. That's probably OK. Setting VERIFIED.
FEDORA-2023-755dc0b0c0 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-755dc0b0c0` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-755dc0b0c0 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-755dc0b0c0 has been pushed to the Fedora 39 stable repository. If problem still persists, please make note of it in this bug report.