Hide Forgot
libreport version: 2.0.6 executable: /usr/bin/python hashmarkername: anaconda kernel: 3.1.0-7.fc16.x86_64 product: Fedora reason: ValueError: No description available for lvmlv time: Tue Nov 22 16:47:30 2011 version: 16 anaconda-tb-3rdxNE: Text file, 217592 bytes description: :The following was filed automatically by anaconda: :anaconda 16.25 exception report :Traceback (most recent call first): : File "/usr/lib64/python2.7/site-packages/pyanaconda/bootloader.py", line 521, in device_description : raise ValueError("No description available for %s" % device.type) : File "/usr/lib64/python2.7/site-packages/pyanaconda/bootloader.py", line 559, in is_valid_stage1_device : description = self.device_description(device) : File "/usr/lib64/python2.7/site-packages/pyanaconda/bootloader.py", line 1529, in is_valid_stage1_device : ret = super(GRUB2, self).is_valid_stage1_device(device) : File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/__init__.py", line 1182, in sanityCheck : self.anaconda.bootloader.is_valid_stage1_device(stage1) : File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/partitioning.py", line 327, in doAutoPartition : (errors, warnings) = anaconda.storage.sanityCheck() : File "/usr/lib64/python2.7/site-packages/pyanaconda/dispatch.py", line 373, in dispatch : self.dir = self.steps[self.step].target(self.anaconda) : File "/usr/lib64/python2.7/site-packages/pyanaconda/text.py", line 508, in run : self.anaconda.dispatch.dispatch() : File "/usr/lib64/python2.7/site-packages/pyanaconda/dispatch.py", line 319, in run : self.anaconda.intf.run(self.anaconda) : File "/usr/sbin/anaconda", line 770, in <module> : anaconda.dispatch.run() :ValueError: No description available for lvmlv
Created attachment 535205 [details] File: anaconda-tb-3rdxNE
Anaconda crashes when I do this in my kickstart: bootloader --location=partition --timeout=11 clearpart --all --initlabel --drives=vda part biosboot --size=1 --ondisk=vda --fstype=biosboot part pv.01 --size=2800 --grow --maxsize=10000000 --asprimary --ondisk=vda volgroup VolGrp01 pv.01 logvol / --label=/ --vgname=VolGrp01 --size=2000 --grow --maxsize=4000 --n ame=root_fs --fstype ext4 logvol /tmp --label=/tmp --vgname=VolGrp01 --size=300 --grow --maxsize=1000 --n ame=tmp_fs --fstype ext4 logvol swap --label=swap --vgname=VolGrp01 --size=500 --grow --maxsize=8000 --n ame=swap --fstype swap If I say, on the bootloader line, location=mbr, then everything is happy. Does the location=partition option not work with LVM? Perhaps I'm confused... it may be that the intention of location=partition is to install the *1st* stage of grub2 to (in this case) the LVM partition, which wouldn't make sense. Still though, anaconda shouldn't crash!
Thinking further on this, perhaps a secondary bug would be that location=mbr isn't descriptive enough on a GPT partitioned disk. Most people don't want to force a hybrid MBR... so they will select anything but "location=mbr". Does "location=mbr" mean "use the biosboot partition if it exists instead of the MBR"? If not, perhaps we could get a "location=biosbootpart" or something similar to avoid both the MBR and large amounts of confusion.
(In reply to comment #3) > Thinking further on this, perhaps a secondary bug would be that location=mbr > isn't descriptive enough on a GPT partitioned disk. Most people don't want to > force a hybrid MBR... so they will select anything but "location=mbr". Anaconda never, ever, does anything related to hybrid MBRs. "mbr" means "install the bootloader's stage1 to the beginning of the disk" which, in the case of GPT means use a BIOS Boot partition. > > Does "location=mbr" mean "use the biosboot partition if it exists instead of > the MBR"? If not, perhaps we could get a "location=biosbootpart" or something > similar to avoid both the MBR and large amounts of confusion. No MBR on GPT. Anaconda doesn't subscribe to hybrid mbr ideas at all. This has gotten a lot less clear with the introduction of gpt and bios boot partitions, revealing that the current syntax was created in a simpler time. I'll make sure it doesn't cause a traceback in the future, but it may take some time to improve the kickstart syntax.
How about just changing "mbr" then to "biosbootpart" ? That seems very descriptive and straight forward.
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. 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 WONTFIX if it remains open with a Fedora 'version' of '16'. 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 prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 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 to click on "Clone This Bug" and open it against that version of Fedora. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Does "location=mbr" mean "use the biosboot partition if it exists instead of the MBR"? If not, perhaps we could get a "location=biosbootpart" or something similar to avoid both the MBR and large amounts of confusion.
Think of "mbr" as meaning "disklabel gap" -- then it applies equally well to both dos and gpt disklabels. Changing this kickstart syntax is a low priority for now.
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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 19 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.
location=partition means "install the stage1 on my /boot partition". If your /boot partition is on lvm, you should have seen an error in the GUI instead of this traceback.
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. 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 '21'. 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 21 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.
Was this ever fixed in the newer installers?
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.