Bug 810141
Summary: | KeyError: 'fstypeCombo' | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Miroslav Franc <mfranc> | ||||
Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> | ||||
Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
Severity: | high | Docs Contact: | |||||
Priority: | high | ||||||
Version: | 17 | CC: | anaconda-maint-list, awilliam, cristian.ciupitu, gareth.k.jones, g.kaviyarasu, jonathan, lkocman, ohudlick, roysjosh, sam, vanmeeuwen+fedora, vondruch | ||||
Target Milestone: | --- | Keywords: | CommonBugs | ||||
Target Release: | --- | ||||||
Hardware: | x86_64 | ||||||
OS: | Unspecified | ||||||
Whiteboard: | abrt_hash:6466520264f49628e15d86921cb0f066a75141f7512c65ee1a1a7f7b1a20ad18 AcceptedNTH https://fedoraproject.org/wiki/Common_F17_bugs#anaconda-btrfs-crash | ||||||
Fixed In Version: | anaconda-18.3 | Doc Type: | Bug Fix | ||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2012-08-03 19:44:31 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: | |||||||
Bug Depends On: | |||||||
Bug Blocks: | 752653 | ||||||
Attachments: |
|
Description
Miroslav Franc
2012-04-05 09:19:20 UTC
Created attachment 575336 [details]
File: anaconda-tb-u1xvMg
*** Bug 810154 has been marked as a duplicate of this bug. *** The same thing happened to me with btrfs (done manually as there is no combo box option for btrfs) Proposing as NTH for F17, since this is rather silly bug. BTRFS was supposed to be default FS for F17, but now, F17 is not possible to install on BTRFS at all. Discussed at 2012-05-04 NTH review meeting. Accepted as NTH as it's a clear visible anaconda bug with concrete consequences and can't be fixed with an update. Might even be considered a blocker. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers This isn't fixed in current RC, so let's commonbugs it at least. AIUI this happens if you try to edit an exist btrfs partition in the custom partitioning editor. (In reply to comment #4) > Proposing as NTH for F17, since this is rather silly bug. BTRFS was supposed > to be default FS for F17, but now, F17 is not possible to install on BTRFS > at all. The way to install with btrfs in F17 is to use kickstart: https://fedoraproject.org/wiki/Anaconda/Kickstart#btrfs This used to work with F16, how come the regression in F17? http://forums.theregister.co.uk/post/1427114 (I happened to write a detailed explanation earlier, figured I'd re-use it). (In reply to comment #9) > http://forums.theregister.co.uk/post/1427114 (I happened to write a detailed > explanation earlier, figured I'd re-use it). Thanks Adam, that's quite informative. Strange that the "back-end" code was merged without the corresponding UI changes.. Am I correct in assuming the best way to install onto btrfs in f17 would be to manually set up the partitioning/volumes, install f16, and do an upgrade? You could just install F16 and use its btrfs to set up the partitioning/volumes (unless you want to use btrfs' native volume support rather than LVM), but sure. Or you can use a kickstart to install F17 with btrfs partitions. *** Bug 826805 has been marked as a duplicate of this bug. *** Is it possible to use Kickstart to install F17 on an *existing* Btrfs-RAID? I'm trying to use kickstart with lines like: # Encrypted mirrored /home. part btrfs.home1 --noformat --encrypted --fstype=btrfs --onpart=sda6 part btrfs.home2 --noformat --encrypted --fstype=btrfs --onpart=sdb4 btrfs /home --noformat btrfs.home1 btrfs.home2 I get an Ananconda error on the first btrfs line that reads "... specified nonexistant BTRFS volume in btrfs command", with a double space between "volume" and "in" as if something is missing. The volumes are definitely formatted though. (Sorry if it's inappropriate to ask that here, but I haven't had any luck searching elsewhere and most relevent pages link back here, so if there is a problem it might help other people as well!) The code this bug resulted from is no longer present as of anaconda-18.3. Please test with F18 and if you see similar problems, open a new bug. Thanks. |