Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
DescriptionValentin Kulesh
2017-03-16 14:43:08 UTC
Description of problem:
which(1) is used by virt-what(1), but not listed in package requirements.
which(1) is not installed by default in RHEL containers, that's how this situation has been detected.
Version-Release number of selected component (if applicable):
1.13-8.el7
How reproducible:
Always
Steps to Reproduce:
1. docker run -it --rm registry.access.redhat.com/rhel7.3
2. yum -y install virt-what
3. virt-what
Actual results:
virt-what: virt-what-cpuid-helper program not found in $PATH
Expected results:
Correct virt-what output.
Additional info:
># Try to locate the CPU-ID helper program
>CPUID_HELPER=$(which virt-what-cpuid-helper 2>/dev/null)
This code fails not because of missing helper, but because of missing which(1)
Already fixed in Fedora 25 as of virt-what-1.15-4.fc25.x86_64
Comment 2Richard W.M. Jones
2017-03-16 15:40:37 UTC
This was fixed in Fedora last year, but not in RHEL.
Verified with package:
virt-what-1.13-10.el7.x86_64
Step:
1. yum -y remove which
2. yum -y install virt-what
------------------------------------
... ...
Dependency Installed:
which.x86_64 0:2.20-7.el7
Updated:
virt-what.x86_64 0:1.13-10.el7
------------------------------------
3. virt-what
In step 2, the which package will be installed when installing virt-what.
In step 3, the command can be executed normally.
So 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://access.redhat.com/errata/RHBA-2017:1952
Description of problem: which(1) is used by virt-what(1), but not listed in package requirements. which(1) is not installed by default in RHEL containers, that's how this situation has been detected. Version-Release number of selected component (if applicable): 1.13-8.el7 How reproducible: Always Steps to Reproduce: 1. docker run -it --rm registry.access.redhat.com/rhel7.3 2. yum -y install virt-what 3. virt-what Actual results: virt-what: virt-what-cpuid-helper program not found in $PATH Expected results: Correct virt-what output. Additional info: ># Try to locate the CPU-ID helper program >CPUID_HELPER=$(which virt-what-cpuid-helper 2>/dev/null) This code fails not because of missing helper, but because of missing which(1) Already fixed in Fedora 25 as of virt-what-1.15-4.fc25.x86_64