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.
DescriptionDanilo de Paula
2020-08-26 18:13:11 UTC
+++ This bug was initially created as a clone of Bug #1872853 +++
qemu-kvm-core depends on glusterfs-api.
But that's wrong.
The only package using glusterfs is qemu-kvm-block-gluster and the dependency should be there instead.
Danilo - assigning this one to you as well for consistency since you have the RHEL-AV bug, but using a Low Priority and no ITR being set.
If this "should" or "needs" to be fixed for RHEL 8.3.0, then we'll need to go through the exception process and we can alter the priority, etc.
(In reply to John Ferlan from comment #1)
> Danilo - assigning this one to you as well for consistency since you have
> the RHEL-AV bug, but using a Low Priority and no ITR being set.
>
> If this "should" or "needs" to be fixed for RHEL 8.3.0, then we'll need to
> go through the exception process and we can alter the priority, etc.
Thank you Jhon,
I can't justify an exception for this in RHEL. It was necessary for AV.
We can fix this in the next rebase in RHEL or in RHEL-8.4
Test with qemu-kvm-core-4.2.0-35.module+el8.4.0+8453+f5da6c50.x86_64.rpm, not hit this issue, so change status to verified.
Version:
qemu-kvm-core-4.2.0-35.module+el8.4.0+8453+f5da6c50.x86_64.rpm
Steps:
1.# rpm -qp qemu-kvm-core-4.2.0-35.module+el8.4.0+8453+f5da6c50.x86_64.rpm --provides
qemu-kvm-core = 15:4.2.0-35.module+el8.4.0+8453+f5da6c50
qemu-kvm-core(x86-64) = 15:4.2.0-35.module+el8.4.0+8453+f5da6c50
2. # rpm -qp qemu-kvm-core-4.2.0-35.module+el8.4.0+8453+f5da6c50.x86_64.rpm --requires | grep glusterfs
Actual result:
After step 2 no match on qemu-kvm-core's dependencies.
Expected result:
Same as Actual result.
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 (Moderate: virt:rhel and virt-devel:rhel security, bug fix, and enhancement update), 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/RHSA-2021:1762