In an installation using the Fedora 15 release candidate with anaconda 15.31, I'm getting the following traceback: Traceback (most recent call first): File "/usr/lib64/python2.7/posixpath.py", line 112, in basename i = p.rfind('/') + 1 File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/formats/__init__.py", line 422, in majorminor device = dm_node_from_name(os.path.basename(self.device)) File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/formats/__init__.py", line 271, in cacheMajorminor self.majorminor # this does the caching File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/devices.py", line 700, in _preTeardown self.format.cacheMajorminor() File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/devices.py", line 714, in teardown if not self._preTeardown(recursive=recursive): File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/devicetree.py", line 1868, in teardownAll device.teardown(recursive=True) File "/usr/lib64/python2.7/site-packages/pyanaconda/packages.py", line 103, in turnOnFilesystems anaconda.storage.devicetree.teardownAll() File "/usr/lib64/python2.7/site-packages/pyanaconda/dispatch.py", line 211, in moveStep rc = stepFunc(self.anaconda) File "/usr/lib64/python2.7/site-packages/pyanaconda/dispatch.py", line 130, in gotoNext self.moveStep() File "/usr/lib64/python2.7/site-packages/pyanaconda/gui.py", line 1346, in setScreen self.anaconda.dispatch.gotoNext() File "/usr/lib64/python2.7/site-packages/pyanaconda/gui.py", line 1476, in setup_window self.setScreen() File "/usr/lib64/python2.7/site-packages/pyanaconda/gui.py", line 1490, in run self.setup_window(False) File "/usr/lib64/python2.7/site-packages/pyanaconda/gui.py", line 1221, in run self.icw.run() File "/usr/sbin/anaconda", line 925, in <module> anaconda.intf.run(anaconda) AttributeError: 'NoneType' object has no attribute 'rfind' Local variables in innermost frame: p: None I will attach the file /tmp/anaconda-tb-MmYD91.
Created attachment 500141 [details] /tmp/anaconda-tb-MmYD91
Is there any other information I can provide that would be helpful? Are there any suggested workarounds for this problem? At the present, I seems that I am unable to install Fedora 15.
I'm getting the same anaconda traceback as above, with the Fedora 15 64-bit release. I'm using a kickstart file too. For me the problem occurs shortly after the message "Examining devices".
*** Bug 707346 has been marked as a duplicate of this bug. ***
When the crash happens, instead of reporting the bug to bugzilla, can someone choose the 'Debug' option. That will drop you into a python debug shell. Once in the shell, please run the following commands and supply the output: > up > print self.device
The debug shell reports that self.device is None.
I also tried going up two more times and doing "print self", which gives a bunch of information about a PartitionDevice instance. The PartitionDevice has a "name" of "sda1", a "format" which is an Ext3FS instance, and a "path" and "device" which are /dev/sda1. I'm sure there's other more useful information, but this seemed like it might be helpful.
Can you describe the disk layout already on the system, please include appropriate command output.
amcnabb@sage:~ :) sudo sfdisk -l /dev/sda [sudo] password for amcnabb: Disk /dev/sda: 77825 cylinders, 255 heads, 63 sectors/track Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0 Device Boot Start End #cyls #blocks Id System /dev/sda1 * 0+ 63- 64- 512000 83 Linux /dev/sda2 63+ 2613- 2550- 20480000 83 Linux /dev/sda3 2613+ 2874- 262- 2097152 82 Linux swap / Solaris /dev/sda4 2874+ 77825- 74951- 602041344 83 Linux amcnabb@sage:~ :) mount |grep sda /dev/sda2 on / type ext4 (rw,relatime,barrier=1,data=ordered) /dev/sda1 on /boot type ext3 (rw,relatime,errors=continue,user_xattr,acl,barrier=0,data=ordered) /dev/sda4 on /local type ext4 (rw,relatime,barrier=1,data=ordered) /dev/sda2 on /tmp type ext4 (rw,relatime,barrier=1,data=ordered) /dev/sda2 on /var/tmp type ext4 (rw,relatime,barrier=1,data=ordered) amcnabb@sage:~ :)
(In reply to comment #9) > amcnabb@sage:~ :) sudo sfdisk -l /dev/sda What does `parted /dev/sda -s p` say?
amcnabb@sage:~ :( sudo parted /dev/sda -s p [sudo] password for amcnabb: Model: ATA SAMSUNG HM640JJ (scsi) Disk /dev/sda: 640GB Sector size (logical/physical): 512B/512B Partition Table: msdos Number Start End Size Type File system Flags 1 1049kB 525MB 524MB primary ext3 boot 2 525MB 21.5GB 21.0GB primary ext4 3 21.5GB 23.6GB 2147MB primary linux-swap(v1) 4 23.6GB 640GB 616GB primary ext4 amcnabb@sage:~ :)
Excellent, thanks for the fast response Andrew! (In reply to comment #7) > I also tried going up two more times and doing "print self", which gives a > bunch of information about a PartitionDevice instance. The PartitionDevice has > a "name" of "sda1", a "format" which is an Ext3FS instance, and a "path" and > "device" which are /dev/sda1. I'm sure there's other more useful information, > but this seemed like it might be helpful. in the debug session, when you are inspecting 'self.format' ... are you able to access the value for 'self.originalFormat'?
Yes, self.originalFormat has "type = ext3" and "device = /dev/sda1". I've left it open, so I can look up any other information from this if needed.
Please try adding 'updates=http://dlehman.fedorapeople.org/updates-706542.img' to your boot command line and see if that helps.
(In reply to comment #14) > Please try adding 'updates=http://dlehman.fedorapeople.org/updates-706542.img' > to your boot command line and see if that helps. This seems to have fixed the problem.
This is the patch contained in the updates image: https://www.redhat.com/archives/anaconda-devel-list/2011-May/msg00234.html
Thank you for addressing the problem. Is the updates image a permanent fix? In other words, is this the best solution to share with others, and can I rely on the image being at this URL for the next year?
The patch has not yet completed the review process, so I cannot say whether or not is permanent. You should not rely on that URL remaining valid for a year. Maybe jlaska has a place for that.
Just for info, the problem hadn't occurred previously when installing f15 beta with the same disk layout and kickstart file. > Please try adding 'updates=http://dlehman.fedorapeople.org/updates-706542.img' > to your boot command line and see if that helps. This fixes the problem for me too. Thanks!
(In reply to comment #17) > Thank you for addressing the problem. Is the updates image a permanent fix? > In other words, is this the best solution to share with others, and can I rely > on the image being at this URL for the next year? Thanks for reporting and testing! I'll document this issue shortly as a CommonBug. I'm discussing with dlehman offline to understand more about the exact failure.
*** Bug 707777 has been marked as a duplicate of this bug. ***
*** Bug 707748 has been marked as a duplicate of this bug. ***
*** Bug 708933 has been marked as a duplicate of this bug. ***
The patch from comment 16 has been applied to the upstream repository and is included in anaconda-16.9-1, so this will be fixed in F16.
Would you please post a permanent url for an updates image for Fedora 15 and add this to the common bugs page? Thanks.
(In reply to comment #25) > Would you please post a permanent url for an updates image for Fedora 15 and > add this to the common bugs page? Thanks. I'm happy to do that ... with some idea for how to reproduce the issue. I still have no idea why you are seeing this, or why I'm not able to reproduce the problem. I'm not saying the issue doesn't exist, just that I don't know enough about it to document it in a sane manner for others. However, we don't need to keep the bug in ASSIGNED until that documentation change is made. I'm moving this back to CLOSED RAWHIDE. I've drafted a *basic* reference to this issue on the wiki at https://fedoraproject.org/wiki/Common_F15_bugs#attributeerror-nonetype. Feel free to adjust as needed.
(In reply to comment #26) > > I'm happy to do that ... with some idea for how to reproduce the issue. I > still have no idea why you are seeing this, or why I'm not able to reproduce > the problem. I'm not saying the issue doesn't exist, just that I don't know > enough about it to document it in a sane manner for others. I think it might be kickstart-related, but I don't know for sure. > I've drafted a *basic* reference to this issue on the wiki at > https://fedoraproject.org/wiki/Common_F15_bugs#attributeerror-nonetype. Feel > free to adjust as needed. I took a look at this description, and I think it's great. Thanks!
*** Bug 711655 has been marked as a duplicate of this bug. ***
*** Bug 715471 has been marked as a duplicate of this bug. ***
*** Bug 751085 has been marked as a duplicate of this bug. ***