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.
Bug 893672 - libvirt-qmf is not properly obsoleted in RHEL 6.4 beta
Summary: libvirt-qmf is not properly obsoleted in RHEL 6.4 beta
Keywords:
Status: CLOSED DUPLICATE of bug 894155
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: libvirt-qmf
Version: 6.3
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: rc
: 6.4
Assignee: Jeff Peeler
QA Contact: Dave Johnson
URL:
Whiteboard:
: 828957 (view as bug list)
Depends On:
Blocks: 830087
TreeView+ depends on / blocked
 
Reported: 2013-01-09 16:43 UTC by Perry Myers
Modified: 2013-01-15 17:59 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-01-15 17:59:41 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Perry Myers 2013-01-09 16:43:07 UTC 
Description of problem:

If you have libvirt-qmf installed in RHEL 6.3 and then update to RHEL 6.4, the new matahari empty package attempts to Obsolete all of the matahari dependencies and _should_ also Obsolete libvirt-qmf

Instead what happens is yum errors out because libvirt-qmf dependencies are removed by the Obsoletes process.  So as of right now the Obsolete logic used by the matahari package is not successfully working

So to replicate:
1. start with RHEL 6.3.z only
2. install libvirt-qmf which pulls in some matahari deps (but not top
   level matahari package)
3. Enable beta channel, disable non-beta
4. yum update

Presence of the empty matahari package in the beta channel will obsolete
the matahari deps brought in via libvirt-qmf but because libvirt-qmf has
deps on specific matahari libraries, the yum transaction will fail

The above error also happens if you do:
1. start with RHEL 6.3.z only
2. install libvirt-qmf which pulls in some matahari deps (but not top
   level matahari package)
2a. Manually install matahari top level package
3. Enable beta channel, disable non-beta
4. yum update

One solution is to create an empty libvirt-qmf RPM in parallel with the empty matahari RPM and then remove the Obsoletes libvirt-qmf line from the matahari spec file.  So this might need to be two different bugs, one for libvirt-qmf and one for matahari
Comment 1 Perry Myers 2013-01-14 13:22:33 UTC 
*** Bug 828957 has been marked as a duplicate of this bug. ***
Comment 4 Zane Bitter 2013-01-14 15:02:32 UTC 
Would adding "Provides: libvirt-qmf" to the (empty) matahari package also fix this? That might be a quicker way.
Comment 6 Jeff Peeler 2013-01-14 16:03:41 UTC 
If I'm understanding correctly, that would work on a new install, but wouldn't solve the upgrade problem (which I just tested).
Comment 8 Perry Myers 2013-01-15 17:59:41 UTC 
It turns out that we were able to fix the string used in the Obsoletes directive in the matahari spec file to properly obsolete libvirt-qmf.  So a new libvirt-qmf build isn't needed and this bug is effectively a duplicate of bug # 894155

Thanks to james from the RPM team for helping us to sort this out :)

*** This bug has been marked as a duplicate of bug 894155 ***
Note You need to log in before you can comment on or make changes to this bug.