RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 590588 - rpm -V fails on chroot dir, /tmp/chroot/var/lib/rpm: No such file or directory
Summary: rpm -V fails on chroot dir, /tmp/chroot/var/lib/rpm: No such file or directory
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: rpm
Version: 6.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Panu Matilainen
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-10 08:59 UTC by Petr Sklenar
Modified: 2011-03-15 13:54 UTC (History)
2 users (show)

Fixed In Version: rpm-4.8.0-8.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-07-02 19:49:46 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Petr Sklenar 2010-05-10 08:59:38 UTC
Description of problem:
rpm -V fails on chroot dir. It writes /tmp/chroot/var/lib/rpm: No such file or directory.

This was fixed in rhel54 in 508074.

Version-Release number of selected component (if applicable):
rpm-4.8.0-6.el6

How reproducible:
always

Steps to Reproduce:
1. yum install installroot=/tmp/chroot rpm -y
# it successfully installs 100megs of packages

2. rpm --root /tmp/chroot -V rpm
  
Actual results:
[root@auto-x86-64-001 ~]# rpm --root /tmp/chroot -Va
S.5....T.  c /etc/pki/nssdb/pkcs11.txt
/tmp/chroot/var/lib/rpm: No such file or directory
[root@auto-x86-64-001 ~]# rpm --root /tmp/chroot -V rpm
/tmp/chroot/var/lib/rpm: No such file or directory
[root@auto-x86-64-001 ~]# rpm -q rpm
rpm-4.8.0-6.el6.x86_64
[root@auto-x86-64-001 ~]# uname -a
Linux auto-x86-64-001.ss.eng.bos.redhat.com 2.6.32-23.el6.x86_64 #1 SMP Tue Apr 27 21:17:28 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux
[root@auto-x86-64-001 ~]# cat /etc/redhat-release 
Red Hat Enterprise Linux release 6.0 Beta (Santiago)

Expected results:
Verification of packages works well on chroot dir

Additional info:

Comment 5 Panu Matilainen 2010-05-18 08:36:52 UTC
Fixed in rpm-4.8.0-8.el6

Comment 7 Petr Beňas 2010-05-24 08:16:20 UTC
Verified on RHEL6.0-20100523.0 i386 and x86_64

:: [   PASS   ] :: Running 'rpm -Va --root /tmp/tmp.nqYVFzBuuD 2> log'
:: [   PASS   ] :: 100. attempt There is no error
:: [   LOG    ] :: Duration: 11m 23s
:: [   LOG    ] :: Assertions: 200 good, 0 bad

Comment 8 releng-rhel@redhat.com 2010-07-02 19:49:46 UTC
Red Hat Enterprise Linux Beta 2 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.


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