libreport version: 2.0.10
cmdline: /usr/bin/python /usr/sbin/anaconda
other involved packages:
release: Cannot get release name.
time: Thu 05 Apr 2012 11:15:42 AM CEST
anaconda-tb-u1xvMg: Text file, 669192 bytes
:The following was filed automatically by anaconda:
:anaconda 17.18 exception report
:Traceback (most recent call first):
: File "/usr/lib64/python2.7/site-packages/pyanaconda/iw/lvm_dialog_gui.py", line 605, in editLogicalVolume
: fmt_class = self.fsoptionsDict["fstypeCombo"].get_active_value()
: File "/usr/lib64/python2.7/site-packages/pyanaconda/iw/partition_gui.py", line 1805, in editLVMLogicalVolume
: vgeditor.editLogicalVolume(lv, isNew = isNew)
: File "/usr/lib64/python2.7/site-packages/pyanaconda/iw/partition_gui.py", line 1668, in editCB
: self.editLVMLogicalVolume(lv = device)
: File "/usr/lib64/python2.7/site-packages/pyanaconda/iw/partition_gui.py", line 1195, in treeActivateCB
:I had f15, tried to install f17. Upon changing already existing logical volume to be mounted as /home, I recieved this traceback.
Created attachment 575336 [details]
*** 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
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:
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.