Red Hat Bugzilla – Bug 1148080
[RFE] Suggest adding 'perf' and/or 'collectl' to the RHEV-H image
Last modified: 2016-07-03 20:41:17 EDT
Description of problem: This is a request to evaluate the potential of adding the 'perf' utility and/or the 'collectl' utility to the RHEV-H image. The reason behind this is that there have been some specific occasions where having these utilities immediately available would have facilitated troubleshooting efforts. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
I understand the need for these tools. (In reply to Gordon Watson from comment #1) … > What we've found is that 'perf' requires the following rpms; … > I think these only use about 40mb of disk space. We have documented the Currently we have about 10MB of space left on the ISO, due to implementation specific limitations. Which means that we can not add those tools.
The limitation is about 256 MegaBytes (base 1024). The installation will fail, because the iso image is larger than the allocated disk-space. The only way to add more packages is by freeing enough space within the iso to add the desired packages.
Hello When you say allocated "disk space" what do you mean exactly. Gordon seems to have been able to create an ISO of 280MB. Thanks Laurence
Yes, the iso can get larger, but it will not fit on the LV on disk. The logical volume on disk, which holds the iso after the installation, is 256MB in size. An iso which is larger than this will not fit into it.
Test version: rhev-hypervisor7-7.2-20151025.0.el7ev ovirt-node-3.3.0-0.18.20151022git82dc52c.el7ev.noarch Test steps: 1. Clean install rhev-hypervisor7-7.2-20151025.0.el7ev 2. Check perf in shell 3. #perf Test result: 1. # rpm -qa perf perf-3.10.0-325.el7.x86_64 2. perf command is provided. So perf package is added in ovirt-node-3.3.0-0.18.20151022git82dc52c.el7ev.noarch now. Change the status to verified.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2016-0378.html