Description of problem: This minimal boot install seems to have failed because the parition label has a non-alphanumeric character in it. The Fedora-18-x86_64-DVD.iso and checksum is stored in /dev/sdb11, an ext3 partition with a label of "/export". Boot a CD with Fedora-18-x86_64-netinst.iso and replace the inst.stage2 option with inst.repo=hd:LABEL=\x2fexport It boots to the language selection screen and after about 30 seconds, the "An unknown error has occured" message pops up. No keys are pressed or mouse movement/clicks were made, so it is easy to reproduce. The Control-Alt-Fkeys still switch screens, so I was able to see that /tmp/storage.log ends with DEBUG storage: failed to resolve 'LABEL=x2fexport' /dev/sdb11 is mounted as /run/install/isodir The iso is mounted as /run/install/repo. cat /proc/cmdline shows initrd=initrd.img inst.repo=hd:LABEL=\x2fexport BOOT_IMAGE=vmlinuz The following was filed automatically by anaconda: anaconda 18.37.11 exception report Traceback (most recent call first): File "/usr/lib64/python2.7/site-packages/pyanaconda/packaging/__init__.py", line 468, in _setupDevice log.info("setting up device %s and mounting on %s" % (device.name, File "/usr/lib64/python2.7/site-packages/pyanaconda/packaging/yumpayload.py", line 522, in _setUpMedia self._setupDevice(device, mountpoint=ISO_DIR) File "/usr/lib64/python2.7/site-packages/pyanaconda/packaging/yumpayload.py", line 602, in _configureBaseRepo self._setUpMedia(isodevice) File "/usr/lib64/python2.7/site-packages/pyanaconda/packaging/yumpayload.py", line 420, in updateBaseRepo self._configureBaseRepo(self.storage, checkmount=checkmount) File "/usr/lib64/python2.7/site-packages/pyanaconda/packaging/yumpayload.py", line 172, in setup self.updateBaseRepo() File "/usr/lib64/python2.7/site-packages/pyanaconda/packaging/__init__.py", line 676, in payloadInitialize payload.setup(storage) File "/usr/lib64/python2.7/threading.py", line 504, in run self.__target(*self.__args, **self.__kwargs) File "/usr/lib64/python2.7/site-packages/pyanaconda/threads.py", line 91, in run threading.Thread.run(self, *args, **kwargs) AttributeError: 'NoneType' object has no attribute 'name' Additional info: cmdline: /usr/bin/python /sbin/anaconda cmdline_file: initrd=initrd.img inst.repo=hd:LABEL=\x2fexport BOOT_IMAGE=vmlinuz executable: /sbin/anaconda hashmarkername: anaconda kernel: 3.6.10-4.fc18.x86_64 other involved packages: package: anaconda-18.37.11 product: Fedora release: Cannot get release name. type: libreport version: 18
Created attachment 682813 [details] File: anaconda-tb
Created attachment 682814 [details] File: anaconda.log
Created attachment 682815 [details] File: environ
Created attachment 682816 [details] File: ifcfg.log
Created attachment 682817 [details] File: packaging.log
Created attachment 682818 [details] File: program.log
Created attachment 682819 [details] File: storage.log
Created attachment 682820 [details] File: syslog
I tried to create a grub2 stanza to boot the install like the Installation Guide Chapter 12.2 shows, but could not get it to work. I then tried to simplify things by using the CDROM to boot the install with the repo= option. I'll change the filesystem label and try again. I have other filesystems with a slash in the label if you want me to reproduce the problem.
I am going to change the title from "AttributeError: 'NoneType' object has no attribute 'name'" to "anaconda repo=hd:LABEL bug with non-alphanumeric characters"
After changing the ext3 partition label to alpha characters only, I was able to perform a Fedora 18 install. This works: repo=hd:LABEL=export and inst.repo=hd:LABEL=export
I was trying to do a kickstart from a local disk, sdb1, otherwise untouched by kickstart. Package: anaconda-18.37.11 OS Release: Fedora release 18
Here are the kickstart commands I used: authconfig --enableshadow --passalgo=sha512 autopart --type=lvm bootloader --boot-drive=sda --location=mbr clearpart --all --drives=sda --initlabel firstboot --disable harddrive --partition=sdb1 --dir=/dev/ISO/Images/Fedora-18-x86_64-DVD ignoredisk --only-use=sda install keyboard --vckeymap=us --xlayouts=us lang en_US.UTF-8 network --bootproto=static --device=em1 --ip=192.168.1.10 --netmask=255.255.255.0 --gateway=192.168.1.1 --nameserver=192.168.1.11,75.75.76.76,75.75.75.75 --noipv6 network --hostname=host.hunter.org rootpw --iscrypted *** timezone America/Chicago --isUtc --ntpservers=0.fedora.pool.ntp.org,1.fedora.pool.ntp.org,2.fedora.pool.ntp.org,3.fedora.pool.ntp.org xconfig --startxonboot Here is how sdb was created: # parted /dev/sdb mklabel gpt # parted /dev/sdb mkpart primary 0GB 100GB set 1 lvm on # parted /dev/sdb mkpart primary 100GB 2000GB set 2 lvm on # parted /dev/sdb print # ssm create --pool ISO --name Images --size 93G --fstype ext4 /dev/sdb1 /var/www/html/Images Did I do something wrong or is this a bug?
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 '18'. 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 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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 to Fedora 18's end of life. 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.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.