Bug 2352385

Created attachment 2080062 [details]
anaconda.log

Created attachment 2080063 [details]
storage.log

Created attachment 2080064 [details]
journal

Created attachment 2080065 [details]
screencast

Just checked with f41,not affected by this bug.

Proposed as a Blocker for 42-final by Fedora user lnie using the blocker tracking app because:

 Affects the  "Remove existing storage volumes" part of custmom_partitioning criteria:
https://fedoraproject.org/wiki/Fedora_42_Beta_Release_Criteria#Custom_partitioning

I believe the dialog hint suggests that the Btrfs device is in use because it contains a Btrfs subvolume. If you delete the subvolume first, you should be able to proceed with removing the device.

yeah,I guess so, but there is no delete button in the choice list,which could be told from the screencast,and the screenshot I'm gonna to attach.

Created attachment 2080216 [details]
screenshot

For the record the device was probably created with:

mkfs.btrfs -L fedora -d single -m single /dev/vda3 /dev/vdb1

This is a missing feature in Cockpit Storage.  Cockpit Storage can not manage the devices of multi-device btrfs filesystems yet.  If you create a multi-device btrfs filesystem externally, Cockpit will let you manage the subvolumes of it, but you can't add or remove devices, nor can you delete the whole thing.

To resolve this bug report, it would be enough to implement erasing a multi-device btrfs filesystem, right?

That should be pretty straightforward, and not involve any of the subtleties that come with raid profiles.

(In reply to Marius Vollmer from comment #11)
> This is a missing feature in Cockpit Storage.  Cockpit Storage can not
> manage the devices of multi-device btrfs filesystems yet.  If you create a
> multi-device btrfs filesystem externally, Cockpit will let you manage the
> subvolumes of it, but you can't add or remove devices, nor can you delete
> the whole thing.
> 
> To resolve this bug report, it would be enough to implement erasing a
> multi-device btrfs filesystem, right?
> 
> That should be pretty straightforward, and not involve any of the subtleties
> that come with raid profiles.

(Randomly chiming in.)

If this is a missing feature in Cockpit, is it reasonable to expect to get this fixed before F42 GA and unblock this? 

Comment#7 indicates there's a workaround of deleting Btrfs sub-volume allows you to delete the full volume.  Can someone confirm this?

@Kashyap, my https://bugzilla.redhat.com/show_bug.cgi?id=2352385#c7 would not solve the issue, I misunderstood the report initially. We need the new feature as described in https://bugzilla.redhat.com/show_bug.cgi?id=2352385#c11 .

Here is a pull request that implements deletion of multi-device btrfs filesystems: https://github.com/cockpit-project/cockpit/pull/21719

> If this is a missing feature in Cockpit, is it reasonable to expect to get this fixed before F42 GA and unblock this? 

I am optimistic that we can land https://github.com/cockpit-project/cockpit/pull/21719 this week.

-4 blocker votes in https://pagure.io/fedora-qa/blocker-review/issue/1793 so rejected as a blocker, but I'm proposing it as an FE as it *would* be good to fix this for Final if we can do so safely.

Discussed during the 2025-03-17 blocker review meeting [1]:

* AGREED: 2352385 - AcceptedFreezeException (Final) - this is accepted as an FE as it's a desirable feature that it would be good to get into F42 if we can land it in enough time to test it. we won't take it very late during freeze

[1] https://meetbot-raw.fedoraproject.org/blocker-review_matrix_fedoraproject-org/2025-03-17/f42-blocker-review.2025-03-17-16.00.log.html

FEDORA-2025-5f443b7585 (cockpit-336-1.fc43) has been submitted as an update to Fedora 43.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-5f443b7585

FEDORA-2025-f696bd8401 (cockpit-336-1.fc42) has been submitted as an update to Fedora 42.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-f696bd8401

FEDORA-2025-d0209082ac (cockpit-336-1.fc41) has been submitted as an update to Fedora 41.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-d0209082ac

FEDORA-2025-5f443b7585 (cockpit-336-1.fc43) has been pushed to the Fedora 43 stable repository.
If problem still persists, please make note of it in this bug report.

FEDORA-2025-f696bd8401 (cockpit-336-1.fc42) has been pushed to the Fedora 42 stable repository.
If problem still persists, please make note of it in this bug report.

FEDORA-2025-d0209082ac has been pushed to the Fedora 41 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-d0209082ac`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-d0209082ac

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

FEDORA-2025-d0209082ac (cockpit-336-1.fc41) has been pushed to the Fedora 41 stable repository.
If problem still persists, please make note of it in this bug report.