Hide Forgot
abrt version: 2.0.5 executable: /mnt/runtime/usr/bin/python hashmarkername: anaconda kernel: 2.6.32-174.el6.i686 product: Red Hat Enterprise Linux reason: TypeError: %d format: a number is required, not NoneType time: Thu Aug 4 15:11:43 2011 version: 6.2 description: :The following was filed automatically by anaconda: :anaconda 13.21.125 exception report :Traceback (most recent call first): : File "/usr/lib/anaconda/storage/devicelibs/edd.py", line 108, in devname_from_pci_dev : 'dev' : self.edd.ata_device : File "/usr/lib/anaconda/storage/devicelibs/edd.py", line 208, in get_edd_dict : name = matcher.devname_from_pci_dev() : File "/usr/lib/anaconda/storage/__init__.py", line 433, in reset : self.eddDict = get_edd_dict(self.partitioned) : File "/usr/lib/anaconda/storage/__init__.py", line 103, in storageInitialize : storage.reset() : File "/usr/lib/anaconda/dispatch.py", line 208, in moveStep : rc = stepFunc(self.anaconda) : File "/usr/lib/anaconda/dispatch.py", line 126, in gotoNext : self.moveStep() : File "/usr/lib/anaconda/gui.py", line 1477, in setScreen : self.anaconda.dispatch.gotoNext() : File "/usr/lib/anaconda/gui.py", line 1390, in nextClicked : self.setScreen () :TypeError: %d format: a number is required, not NoneType
Got this crash at disk initialization when attempting to install a latest RHEL 6.2 Xen full-virt guest. There were no problems with a Xen paravirt guest.
I was also able to "convert" the successfully installed paravirt guest to a full-virt guest using the following steps. 1) destroy the config for the paravirt guest, but not the disk image 2) virt-install using the RHEL 6.1 release for the repo and the old paravirt guest disk image for the disk image 3) select update instead of reinstall and to rewrite the boot loader 4) anaconda immediately says the update is complete (since the image actually has packages that are all >= to 6.1) and prompts for reboot 5) the reboot succeeds and the guest works fine, already running on the -174 kernel
(note that the attachment is missing here because of bug 727243)
Andrew, Thanks for reporting this, can you please attach all /sys/firmware/edd/int13_dev*/host_bus or confirm the files do not exist? Thank you.
I had already destroyed the failed guest, so I had to try and recreate it. This time it successfully installed and booted from the 6.2 nightly repo I used, which has anaconda-13.21.126-1.el6.i686
Nevermind, i had a fix ready for that scenario and since I believe it can occur on some machines (unfortunately including xen) I'll go ahead with it.
Posted a patch with a unit test and a fix. The unit test reproduces the traceback from comment 0: https://www.redhat.com/archives/anaconda-devel-list/2011-August/msg00079.html David, can you obtain the acks for this bug please?
Granting QA ack, but we're unable to reproduce this bug, so only sanity testing will be done.
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release.
fixed by 914d798acdca75ccaf238671d228f80eebb17246 (a02c624673fdc3311f64ba270426006b5261c9cb on master)
I wasn't able to reproduce. With anaconda-13.21.128 I can successfully install Xen FV guest and the patch is present in the code. Setting Verified=SanityOnly.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2011-1565.html