Bug 5019 - Upgrade Fails on a 6.0
Upgrade Fails on a 6.0
Status: CLOSED CURRENTRELEASE
Product: Red Hat Linux
Classification: Retired
Component: installer (Show other bugs)
6.1
i386 Linux
medium Severity high
: ---
: ---
Assigned To: Jay Turner
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 1999-09-09 07:06 EDT by jharris
Modified: 2015-01-07 18:38 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 1999-12-06 10:13:43 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)

  None (edit)
Description jharris 1999-09-09 07:06:01 EDT
Using Lorax to upgrade a 6.0 system cause a system
hang/crash. In the second stage of the install the system
hangs while searching installed packages.  From the script
output a permision error is seen while trying to call
makeinode in of the python scripts. So it appears that the
script is attempting to write something where it can't
Comment 1 jharris 1999-09-13 00:31:59 EDT
Some more debug info I have found. The error output from the install
is
File "/usr/lib/python1.5/site-packages/isys.py" Line 63 in
makeDevinode
return _isys.mkdevinode(name,fn)
SystemError (2,No such file or directory);

The whole calling chain was displayed.. but I thought was the relevent
portion.
Comment 2 Jay Turner 1999-12-06 10:13:59 EST
By any chance do you have /tmp symlinked to somewhere?  There is a problem in
the installer (which is really hard to workaround unfortunately) that the
installer is not able to follow absolute symlinks.  It is fine with relative
symlinks, so if you have an absolute symlink, just change it to be a relative
one and your install should work fine.  I am marking this bug a duplicate of
#6141.  Please reopen if the symlink change does not resolve the problem.

*** This bug has been marked as a duplicate of 6141 ***

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