As shown in the attached,boot with Fedora-Workstation-Live-osb-40-20240219.n.0.x86_64.iso,on Configure Storage page,click into the mdraid device,but "Not found" is shown, so users won't be able to delete the device. Reproducible: Always
Created attachment 2017926 [details] screencast
Created attachment 2017927 [details] storage.log
Created attachment 2017928 [details] anaconda.log
Proposed as a Blocker for 40-beta by Fedora user lnie using the blocker tracking app because: violates https://fedoraproject.org/wiki/Fedora_40_Beta_Release_Criteria#Custom_partitioning
Fedora-Workstation-Live-osb-40-20240219.n.0.x86_64.iso is not a release-blocking image, it's the experimental osbuild-built one. The official one doesn't have 'osb' in the name. That *probably* doesn't matter, but please use the non-osbuild one for testing potential blockers. More importantly, the webui change got deferred by FESCo , so webui-specific issues shouldn't block F40 any more. We didn't actually make the change on the images yet, I need to work that out with desktop and releng...
> That *probably* doesn't matter Yeah, checked with Fedora-Workstation-Live-x86_64-40-20240219.n.0.iso,same symptom. > the webui change got deferred by FESCo, so webui-specific issues shouldn't block F40 any more. Thanks for your info,I do feel there are lots of bug in web ui,gonna to remove this bug from blocker list.
Thanks! This is a bug in the Anaconda mode of Cockpit-Storage: it uses the same mechanism to decided whether or not show mdraids that it also uses for ordinary block devices.
(In reply to lnie from comment #6) > Thanks for your info,I do feel there are lots of bug in web ui,gonna to > remove this bug from blocker list. I think it works pretty well, all things considered.
(In reply to Marius Vollmer from comment #7) > Thanks! This is a bug in the Anaconda mode of Cockpit-Storage: it uses the > same mechanism to decided whether or not show mdraids that it also uses for > ordinary block devices. That was actually not the reason. Most likely the MDRaid page was omitted because your mdraid device was stopped. Cockpit would erroneously give up and not try to determine whether or not the mdraid was part of the target environment, and simply decide to hide it. At the time we probably didn't consider this an important case, but it turns out that Anaconda itself is tearing down all kinds of storage things and I wouldn't be surprised if it also stops all mdraids that it finds. Should be fixed by https://github.com/cockpit-project/cockpit/pull/20073
FEDORA-2024-4ce0aa04c1 (cockpit-312-1.fc40) has been submitted as an update to Fedora 40. https://bodhi.fedoraproject.org/updates/FEDORA-2024-4ce0aa04c1
FEDORA-2024-4ce0aa04c1 has been pushed to the Fedora 40 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-4ce0aa04c1` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-4ce0aa04c1 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2024-6108f04e95 has been pushed to the Fedora 40 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-6108f04e95` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-6108f04e95 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2024-6108f04e95 (cockpit-313-1.fc40) has been pushed to the Fedora 40 stable repository. If problem still persists, please make note of it in this bug report.