Bug 496927
Summary: | Anaconda leaves a broken install | ||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Andrew McNabb <amcnabb> | ||||||||||||||||
Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> | ||||||||||||||||
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||||
Severity: | high | Docs Contact: | |||||||||||||||||
Priority: | low | ||||||||||||||||||
Version: | 11 | CC: | anaconda-maint-list, pjones, rmaximo, vanmeeuwen+fedora | ||||||||||||||||
Target Milestone: | --- | ||||||||||||||||||
Target Release: | --- | ||||||||||||||||||
Hardware: | i386 | ||||||||||||||||||
OS: | Linux | ||||||||||||||||||
Whiteboard: | |||||||||||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||||||
Doc Text: | Story Points: | --- | |||||||||||||||||
Clone Of: | Environment: | ||||||||||||||||||
Last Closed: | 2010-06-28 12:09:06 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: | |||||||||||||||||||
Attachments: |
|
Description
Andrew McNabb
2009-04-21 16:44:02 UTC
Created attachment 340574 [details]
kickstart script used for install
Created attachment 340575 [details]
anaconda.log
Created attachment 340576 [details]
anaconda.syslog
Created attachment 340577 [details]
anaconda.xlog
Created attachment 340578 [details]
anaconda-ks.cfg
Created attachment 340579 [details]
install.log
Created attachment 340580 [details]
install.log.syslog
Hrm, this is strange. I see nothing in your log files to indicate how this could have gotten so screwed up. Is it reproducable? My best guess is that your mirror was syncing rawhide at the same moment you were trying to install from it, so things got confused and you ended up with a very broken package set. Strangely, there aren't any scriptlet errors in your install.log. Unfortunately, it was a miracle that I was able to get it installed at all because of some unrelated partitioning/formatting errors (I had Anaconda crash 5 or 6 times along the way and had to restart the install each time). I ended up reinstalling without a kickstart script at all, and things worked much better. I'd be happy to try reproducing in a few days after the Anaconda partitioning bugs get fixed and pushed. I looked at the logs on the mirror, and it looks like it finished syncing at about 5 am (long before I performed the installation), so I don't think that could be the problem. I noticed that there are a number of open kickstart-related bugs, so I wonder if it might be a matter of building the package list incorrectly when kickstart is being used. When I did the install with kickstart, I remember seeing in the progress bar that it was trying to install about 1000 messages, but when I installed without kickstart, I think the number of packages was more like 1500. Theoretically it should be the same because the kickstart was an interactive install and because I picked the same options. The "failed to read image" message is still happening even after reinstalling, so I've filed a separate bug report (bug #497146). This bug really seems to be just about package selection. This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle. Changing version to '11'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping This message is a reminder that Fedora 11 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 11. 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 '11'. 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 11's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 11 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 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. Thank you for reporting this bug and we are sorry it could not be fixed. |