Red Hat Bugzilla – Bug 439270
failure to select /boot terminates install
Last modified: 2008-05-21 11:33:44 EDT
Description of problem:
If the user fails to setup a /boot mount point before leaving
the Create Custom Layout screen, the installation terminates
with an exception.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. for partitions, choose Create Custom Layout
2. setup the / mount point
3. do not setup a /boot mount point
4. choose [OK]
Anaconda gives the following traceback:
+--------------+ Exception Occurred +--------------+
| Traceback (most recent call first): ^ |
| File "/usr/lib/anaconda/fsset.py", line # |
| 2986, in getDiskPart : |
| if dev[-2] in string.digits: : |
| File "/usr/lib/anaconda/partitions.py", : |
| line 867, in sanityCheckAllRequests : |
| (dev, num) = fsset.getDiskPart(br.device) : |
| File : |
| "/usr/lib/anaconda/textw/partition_text.py", : |
| line 1489, in __call__ : |
| (errors, warnings) = : |
| self.partitions.sanityCheckAllRequests(self.d v |
| +----+ +-------+ |
| | OK | | Debug | |
| +----+ +-------+ |
Anaconda should allow the user to correct the problem and
continue with the install.
Can you please attach the complete traceback to this bug report? You can find
this in /tmp/anacdump.txt.
Is there a way to get that information from the debugger? The install fails
before it has a chance to format the root partition.
Here's a bit more seen after choosing [Debug].
Traceback (most recent call first):
File "/usr/lib/anaconda/fsset.py", line 2986, in getDiskPart
if dev[-2] in string.digits:
File "/usr/lib/anaconda/partitions.py", line 867, in sanityCheckAllRequests
(dev, num) = fsset.getDiskPart(br.device)
File "/usr/lib/anaconda/textw/partition_text.py", line 1489, in __call__
(errors, warnings) = self.partitions.sanityCheckAllRequests(self.diskset)
File "/usr/lib/anaconda/text.py", line 565, in run
rc = win(self.screen, instance)
File "/usr/bin/anaconda", line 982, in ?
IndexError: string index out of range
I don't know this code, but do you need to sanity check either bootreqs or
br.device before calling fsset.getDiskPart() at partitions.py: 867?
There is a complete traceback report in /tmp/anacdump.txt that anaconda also
prompts you to save to a remote system when the exception occurs. This file
contains a full dump of the state of internal anaconda variables, so we can see
things like what dev was when it tried to subscript it (though I'm guessing it
was blank or perhaps None) and other things like that.
Okay, I see what's going on here and have a patch that fixes this issue.
Okay good, because I don't get the prompt to save off the dump file (maybe too
early in the install?)
VERIFIED using snap#3 and http://people.redhat.com/clumens/439270.img
* Tested removing /boot and proceeding with / as a logical volume (error dialog
* Tested removing /boot and proceeding with / as ext3
This will be fixed in anaconda-18.104.22.168.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.