Bug 826268
Summary: | ValueError: Cannot remove non-leaf device 'vg_orthanc_ssd-root_fs' | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | David Mansfield <bugzilla> | ||||
Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> | ||||
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
Severity: | unspecified | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | 17 | CC: | anaconda-maint-list, g.kaviyarasu, jonathan, vanmeeuwen+fedora | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | x86_64 | ||||||
OS: | Unspecified | ||||||
Whiteboard: | abrt_hash:9b2cc139d65041ea5c504b92238227f8141bd481287afeaecbf9af0e36cb2de6 | ||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2012-05-31 15:34:10 UTC | Type: | --- | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
David Mansfield
2012-05-29 21:36:21 UTC
Created attachment 587534 [details]
File: anaconda-tb-d9llDn
This is an installer crash. It's reproducible. I cannot install F17 due to this bug. Scenario: I want to install a fresh F17 in an existing system. I have many LV on 2 VG. I also have a partition /dev/sda1 for /boot. I'd like to re-format and install onto 3 LV (on different VG) plus the /boot partition, and mount some of the others. The mounting can be deferred to later, assuming I can get past this bug. The LV in question are currently formatted btrfs via the F16 (or F15, can't remember) installer. Some of the other LV are also btrfs. When selecting them in the "edit vg" menu, I cannot choose to re-format the LV, the option is grayed out. Also, I tried deleting the LV and re-adding with a different FS-type. Resulted in "same" crash (I say same because I don't have the traceback of both). Seems probably a bug because btrfs doesn't seem to be a valid "fs type" in this release. Unfortunately, we had to temporarily reduce our support for btrfs in F17 due to some resource constraints and upstream work planned for F18. In F18 you will see a completely new user interface for the installer, including full support for all of the major btrfs features like subvolumes and RAID. Sorry for the inconvenience. In the meantime, see https://fedoraproject.org/wiki/Anaconda/Kickstart#btrfs for the only way to use btrfs in F17: kickstart. I was able to complete an installation as long as no LV that contained BTRFS was "touched" during installation, e.g. I did not remove, reformat or mount any of them, just installed on new LV in the same VG. assuming it won't be fixed and marking appropriately. |