Bug 616119 - Convert RHEVH blacklisting to completely use the appliance-tools image minimizer utility
Convert RHEVH blacklisting to completely use the appliance-tools image minimi...
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: ovirt-node (Show other bugs)
All Linux
low Severity medium
: rc
: ---
Assigned To: Alan Pevec
Virtualization Bugs
Depends On: 616737
Blocks: 614870 616121
  Show dependency treegraph
Reported: 2010-07-19 13:35 EDT by Perry Myers
Modified: 2010-11-11 09:52 EST (History)
3 users (show)

See Also:
Fixed In Version: ovirt-node-1.9.3-5.git3a9e2d0.el6
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 616121 (view as bug list)
Last Closed: 2010-11-11 09:52:48 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Perry Myers 2010-07-19 13:35:23 EDT
Description of problem:
Blacklisting of files in RHEVH presently is done by both some image minimimzer directives but also by explicitly rm -f commands.

In order to make it easier to do derivative spins of RHEVH we need to move to using the image minimizer for all blacklisting operations.
Comment 2 Mohua Li 2010-08-23 05:37:20 EDT
as i have never  build rhev-h, never use image-minimimzer to drop/keep rpms for rhev-h, can someone tell me where can i find the blacklist conf file, and  now if we compeletely use the image-minimimzer instead of rm -rf to blacklist the rpms  to build the rhev-h?
Comment 3 Alan Pevec 2010-08-23 06:04:03 EDT
look at common-blacklist.ks and common-minimizer.ks in ovirt-node-tools
Comment 4 Mohua Li 2010-08-24 05:27:12 EDT
check in ovirt-node-tools-1.9.3-8.gitb16b938.el6.noarch,  i did find these two files, 

[root@dhcp-66-70-73 ~]# rpm -ql ovirt-node-tools-1.9.3-8.gitb16b938.el6.noarch

it do, drop/keep some rpms, so it's fixed,
Comment 5 releng-rhel@redhat.com 2010-11-11 09:52:48 EST
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.