Bug 454523

Summary: yum --installroot fails: Could not open ts_done file: [Errno 2] No such file or directory: '/var/lib/yum/transaction-done
Product: Red Hat Enterprise Linux 5 Reporter: Jess Cannata <jac67>
Component: yumAssignee: James Antill <james.antill>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: medium Docs Contact:
Priority: low    
Version: 5.2CC: mpaesold
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-03-25 01:46:00 EDT Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:

Description Jess Cannata 2008-07-08 17:31:00 EDT
Description of problem:

Using yum to install in a chrooted environment with --installroot no longer
works. It complains of <chroot_dir>/var/lib/yum not existing. The yum package
should create this directory (/var/lib/yum), but it doesn't. This used to work.
If you create <chroot_dir>/var/lib/yum, it will work.

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


How reproducible: Always


Steps to Reproduce:

1. mkdir /tmp/test

2. rpm -ivh --nodeps --root /tmp/test redhat-release-5Server-5.1.0.2.x86_64.rpm
 redhat-release-notes-5Server-9.x86_64.rpm

3. yum -y --installroot=/tmp/test/ install yum

Actual results:

Running Transaction
  Installing: glibc-common                 ####################### [ 1/70]
error: %post(glibc-common-2.5-24.i386) scriptlet failed, signal 2
could not open ts_done file: [Errno 2] No such file or directory:
'/tmp/test//var/lib/yum/transaction-done.2008-07-08.17:24.01'

The same error repeats for every package.

Expected results:

  Installing: glibc-common                   ####################### [ 1/70]
  Installing: gpm                            ####################### [ 2/70]

Additional info: This used to work in previous versions of RHEL.
Comment 1 James Antill 2009-03-25 01:46:00 EDT
This was fixed in 3.2.19 in 5.3