Bug 180597 - FC5t2 upgrade from FC4 failed after checking dependencies
FC5t2 upgrade from FC4 failed after checking dependencies
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: anaconda (Show other bugs)
5
i386 Linux
medium Severity high
: ---
: ---
Assigned To: Anaconda Maintenance Team
Mike McLean
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2006-02-09 02:00 EST by Jeremy Fitzhardinge
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-02-09 08:13:34 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
Exception info (97.01 KB, text/plain)
2006-02-09 02:00 EST, Jeremy Fitzhardinge
no flags Details

  None (edit)
Description Jeremy Fitzhardinge 2006-02-09 02:00:28 EST
Created attachment 124425 [details]
Exception info
Comment 1 Jeremy Fitzhardinge 2006-02-09 02:00:28 EST
Description of problem:
I'm doing a PXE/NFS update of my laptop from FC5t2 downloaded today.  It starts
up OK, but after asking the initial questions, finding my FC4 installation and
doing the dependency analysis, it dies with an exception, apparently trying to
create /mnt/sysimage/dev/root.

Version-Release number of selected component (if applicable):
FC5t2 

How reproducible:
Always.

Steps to Reproduce:
1. PXE boot target machine
2. Use NFS as install source
3. Go through screens until "finding package dependencies"
  
Actual results:
Crashes with exception.

Expected results:
Update should start.

Additional info:
Comment 2 Jeremy Fitzhardinge 2006-02-09 02:14:19 EST
If I manually remove /mnt/sysimage/dev/root after anaconda mounts /mnt/sysimage
but before install-proper starts, it seems to work OK.  It gets further at least.
Comment 3 Paul Nasrat 2006-02-09 08:13:34 EST
I fixed this yesterday should be in todays rawhide tree.

Note You need to log in before you can comment on or make changes to this bug.