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.

Description of problem:
Query installed packages with --whatprovides rpm option rather than only with -q.
Use cases:
1. libjpeg package in RHEL6.4 will be replaced by libjpeg-turbo, so Host installation will not find libjpeg package once It queries "rpm -q libjpeg". Adding --whatprovides option should output the right provider of libjpeg - libjpeg-turbo.
2. If qemu-kvm-rhev is installed on the host, queiryng "rpm -q qemu-kvm" gives a warning even though qemu-kvm-rhev provides qemu-kvm.

I may be indeed missing something but It looks to me a better idea to query packages with the option --whatprovides.

Version-Release number of selected component (if applicable):
vdsm-4.9.6-41.0

How reproducible:
Always

Steps to Reproduce:
1. Install a host with qemu-kvm-rhev or libjpeg-turbo into RHEVM.
  
Actual results:
Warnings about not installed packages for either qemu-kvm-rhev and family or libjpeg

Expected results:
It should not warn or fail the installation since needed binaries, libraries are provided by qemu-*-rhev or libjpeg-turbo.

Additional info:

Ad: 2. As I am thinking, maybe RHEVM should require qemu-*-rhev rather than qemu-*. Then qemu-kvm should be changed in VDS_PACK tuple to qemu-kvm-rhev. Anyway using --whatprovides is still better at least for libjpeg-turbo case and any similar.

Hello,

3.2 will have a complete rewritten bootstrap.
Part of the rewrite contains already merged upstream usage of yum API to install packages.
It will install all packages in a single transaction within explicit adding the dependencies.

Alon.

*** This bug has been marked as a duplicate of bug 861575 ***