libreport considers this a dupe of 960271, but I don't think it really is: both crashes occur "in File "/usr/lib/python2.7/site-packages/blivet/devices.py", line 789, in create raise DeviceCreateError(str(e), self.name)", but the actual errors are rather different. This one's nice and easy to reproduce: all you have to do is run an install with the kickstart http://www.happyassassin.net/extras/btrfs_test.ks . The partitioning lines in the kickstart were derived from https://bugzilla.redhat.com/show_bug.cgi?id=799154 (I was trolling through old anaconda bug reports, and it seemed like a good idea to see if that kickstart would work with current anaconda). It fails every time for me. Tested with 19 Beta TC3 and TC4. Traceback (most recent call last): File "/usr/lib64/python2.7/site-packages/pyanaconda/threads.py", line 141, in run threading.Thread.run(self, *args, **kwargs) File "/usr/lib64/python2.7/threading.py", line 766, in run self.__target(*self.__args, **self.__kwargs) File "/usr/lib64/python2.7/site-packages/pyanaconda/install.py", line 117, in doInstall turnOnFilesystems(storage, mountOnly=flags.flags.dirInstall) File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 162, in turnOnFilesystems storage.doIt() File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 303, in doIt self.devicetree.processActions() File "/usr/lib/python2.7/site-packages/blivet/devicetree.py", line 237, in processActions action.execute() File "/usr/lib/python2.7/site-packages/blivet/deviceaction.py", line 272, in execute self.device.create() File "/usr/lib/python2.7/site-packages/blivet/devices.py", line 789, in create raise DeviceCreateError(str(e), self.name) DeviceCreateError: ('1', 'f17')
Created attachment 746413 [details] traceback
Created attachment 746414 [details] anaconda.log
Created attachment 746416 [details] program.log
Created attachment 746417 [details] packaging.log
Created attachment 746418 [details] ifcfg.log
Created attachment 746419 [details] syslog
Created attachment 746420 [details] storage.log
Proposing as an FE as this kind of crasher seems like a good thing to get fixed.
The error btrfs returns is: unable to create FS with metadata profile 16 (have 1 devices) IOW you can't have metadata profile of raid1 if you have only one member device.
Ah - so: btrfs none --data=0 --metadata=1 --label=f17 btrfs.01 makes this an invalid configuration? My bad, I missed what that '--metadata' meant. Does that make this notabug, or would you expect some more graceful kind of failure?
Discussed at 2013-05-15 freeze exception review meeting: http://meetbot.fedoraproject.org/fedora-blocker-review/2013-05-15/f19beta-blocker-review-6.2013-05-15-16.02.html . This was accepted as a freeze exception issue, but I'll delay applying that status as it seems the error may be more a nonsense kickstart than anything.
It would be better if we showed an error message instead of a traceback, but I think it's still a fatal error.
dlehman says ideally we could improve this to provide more useful feedback to the user, so leaving it open, but moving to rawhide and dropping FE status to reflect the lack of urgency.
This bug appears to have been reported against 'rawhide' during the Fedora 20 development cycle. Changing version to '20'. More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora20
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
See commits for bz#1019685.