Bug 439270
Summary: | failure to select /boot terminates install | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Amy Griffis <amy.griffis> |
Component: | anaconda | Assignee: | Chris Lumens <clumens> |
Status: | CLOSED ERRATA | QA Contact: | Alexander Todorov <atodorov> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 5.2 | CC: | amy.griffis, dchapman, jlaska, martine.silbermann, rick.hester |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | RHBA-2008-0397 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-05-21 15:33:44 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Amy Griffis
2008-03-27 19:53:53 UTC
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 ? anaconda.intf.run(anaconda) 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 properly displayed) * Tested removing /boot and proceeding with / as ext3 This will be fixed in anaconda-11.1.2.111. 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. http://rhn.redhat.com/errata/RHBA-2008-0397.html |