Bug 596718 - remove rpmdb from RHEV-H image
Summary: remove rpmdb from RHEV-H image
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: ovirt-node
Version: 6.0
Hardware: All
OS: Linux
Target Milestone: rc
: ---
Assignee: Alan Pevec
QA Contact: Virtualization Bugs
Depends On:
Blocks: 596721
TreeView+ depends on / blocked
Reported: 2010-05-27 11:28 UTC by Alan Pevec
Modified: 2010-11-11 14:52 UTC (History)
4 users (show)

Clone Of:
: 596721 (view as bug list)
Last Closed: 2010-11-11 14:52:38 UTC

Attachments (Terms of Use)

Description Alan Pevec 2010-05-27 11:28:16 UTC
Description of problem:
rpm tool and its database should be removed from RHEV-H to decrease the image size.
/var/lib/rpm is taking >10MB and it's useless except for debugging and during development.

NVRs of installed package are available in the manifest generated during the build and stored in isolinux/manifest-{s,}rpm.txt

Comment 2 RHEL Product and Program Management 2010-05-27 21:16:12 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for

Comment 5 Vivian Bian 2010-08-23 05:05:50 UTC
checked with rhev-hypervisor-6.0-12

1.boot into firstboot menu -> support menu -> shell 
2.grep rpmdb /live/isolinux/manifest-{s,}rpm.txt
3.rpm -qa
  error: cannot open Packages database in /var/lib/rpm
  error: cannot open Packages database in /var/lib/rpm

actual result:
there is no rpmdb available in rhevh , rpmdb is removed from RHEVH image . 

set bug status to VERIFIED

Comment 7 releng-rhel@redhat.com 2010-11-11 14:52:38 UTC
Red Hat Enterprise Linux 6.0 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.