Bug 3823 – upgrade to 6.0 failed due to link pb

Bug 3823 - upgrade to 6.0 failed due to link pb

Summary:	upgrade to 6.0 failed due to link pb

Status:	CLOSED NOTABUG

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	installer (Show other bugs)
Sub Component:
Version:	6.0
Hardware:	i386 Linux

Priority	low Severity high
Target Milestone:	---
Target Release:	---
Assigned To:	Matt Wilson
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	1999-06-30 06:57 EDT by proux
Modified:	2008-05-01 11:37 EDT (History)
CC List:	1 user (show)

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

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description proux 1999-06-30 06:57:14 EDT

In the very begining 6.0 installation script, installation
try to
find rpmdatabase in /var/lib/rpm/packages.rpm
But on my system /var is a link to /tmp_var/var (I've got
one filesystem to /var and /tmp, /tpm is an other link to
/tpm_var/tmp).
I think, installation try to find packages.rpm on
/mnt/var/lib/rpm/packages.rpm
but for me, it will become /tmp_var/var/lib/rpm/packages.rpm
and this file is not find out there. It shoud be
/mnt/tmp_var/var/lib/rpm/packages.rpm
So instalation failed. If I recreate a normal /var every
think is allright !

Comment 1 Jay Turner 1999-06-30 08:12:59 EDT

Installer is unable to find the RPM database when it is located on a
symbolically linked volume.  This issue has been forwarded to the
installer developer for further action.

Comment 2 Jeff Johnson 1999-06-30 19:07:59 EDT

Make sure you use a relative link as in

	cd /
	ln -sf tmpvar/var var

Please reopen if this doesn't fix the problem.

Comment 3 proux 1999-07-01 03:20:59 EDT

It's already a symbolic link !

Comment 4 Jay Turner 2000-02-10 16:13:59 EST

This issue is a result of the symbolic link being absolute instead of relative.
This is what causes the problem.  Changing the link from an absolute to a
relative link will solve the problem.

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