Bug 212575
Summary: | Upgrading from FC5 to FC6 locks up at dependency check | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Răzvan Sandu <rsandu2004> |
Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> |
Status: | CLOSED DUPLICATE | QA Contact: | |
Severity: | urgent | Docs Contact: | |
Priority: | medium | ||
Version: | 6 | CC: | bes.wll, james, rsandu2004 |
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: | 2006-11-03 01:11:36 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
Răzvan Sandu
2006-10-27 15:34:05 UTC
I had this happen to me as well, I just left the system alone for about 45 minutes and it fixed its self. Also, beware that if you are upgrading from FC5 to FC6, it will take an extra long time to update (the ETA reached 350 minutes or more). It happened to me as well. Installation from DVD. When about 75% (after about 3 hours) of my update from FC5 was ready, it just stopped. No messages, just the rotating mouse pointer was there. I waited a further 2 hours and the decided to force a reboot, once again started the installation. This time everything went through. One observation though: Several times during the installation a dependency check with a progress bar is shown. In the last 3(?) times of this window the progress bar remains at zero (=no progress) but nevertheless the installation goes on. Does it lock up or does it just take a long time? Thank you for your responses. Indeed, it doesn't lock up, just last painfully long and dirts the screen with the quoted message. However, it seems there *are* some bugs around in anaconda or yum ;-) - see bug #212180 which I also experienced. Regards, Razvan *** This bug has been marked as a duplicate of 211896 *** |