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 916257 - Yum update failing rpm dep. check (matahari and it's deps.)
Summary: Yum update failing rpm dep. check (matahari and it's deps.)
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: yum
Version: 6.5
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: rc
: ---
Assignee: Packaging Maintenance Team
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
: 916513 917249 918125 952760 954330 966763 970439 987564 998029 1004964 1009837 1015195 1039043 1102280 1117987 1160231 1185184 1186552 1320291 1379364 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-02-27 16:20 UTC by Kevin Northcutt
Modified: 2018-12-09 16:56 UTC (History)
21 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-07-24 06:14:29 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Kevin Northcutt 2013-02-27 16:20:10 UTC 
Description of problem:I receive this every time I run yum update.
Running rpm_check_debug
ERROR with rpm_check_debug vs depsolve:
libqpidclient.so.5()(64bit) is needed by (installed) matahari-net-0.4.0-5.el6.x86_64
libqpidcommon.so.5()(64bit) is needed by (installed) matahari-net-0.4.0-5.el6.x86_64
libmcommon.so.0.0.1()(64bit) is needed by (installed) matahari-net-0.4.0-5.el6.x86_64
libmnet.so.0.0.1()(64bit) is needed by (installed) matahari-net-0.4.0-5.el6.x86_64
matahari-lib = 0.4.0-5.el6 is needed by (installed) matahari-net-0.4.0-5.el6.x86_64
libmqmfagent.so.0.0.1()(64bit) is needed by (installed) matahari-net-0.4.0-5.el6.x86_64
matahari-agent-lib = 0.4.0-5.el6 is needed by (installed) matahari-net-0.4.0-5.el6.x86_64


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


How reproducible: ru yum update


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 2 James Antill 2013-02-27 20:33:13 UTC 
 What does "yum check" say? What is the full output?
Comment 3 RHEL Program Management 2013-03-03 06:47:47 UTC 
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
Comment 4 Richard Robinson 2013-03-10 17:13:43 UTC 
I had a similar problem (updating on RHEL 6.1). I resolved it doing this:

yum shell
> install matahari
> remove matahari-service
> remove matahari-lib
> remove matahari-host
> remove matahari-agent
> remove matahari-net
> run
> exit

NOTE: in my case the above mentioned remove packages were what were mentioned on the yum update output. Your output (and packages needed to remove) may vary.

See http://agilesysadmin.net/advanced-dependency-management for more.
Comment 6 James Antill 2013-04-09 20:55:25 UTC 
*** Bug 918125 has been marked as a duplicate of this bug. ***
Comment 7 James Antill 2013-04-09 20:55:41 UTC 
*** Bug 917249 has been marked as a duplicate of this bug. ***
Comment 8 James Antill 2013-04-09 20:56:58 UTC 
*** Bug 916513 has been marked as a duplicate of this bug. ***
Comment 9 Ryan Galkowski 2013-04-16 14:37:27 UTC 
The Matahari agent framework (matahari-*) packages are deprecated starting with the Red Hat Enterprise Linux 6.3 release. Focus for remote systems management has shifted towards the use of the CIM infrastructure. This infrastructure relies on an already existing standard, which provides a greater degree of interoperability for all users. It is strongly recommended that users discontinue the use of the matahari packages and other packages which depend on the Matahari infrastructure (specifically, libvirt-qmf and fence-virtd-libvirt-qpid). It is recommended that users uninstall Matahari from their systems to remove any possibility of security issues being exposed.

Therefore the proper fix is:
yum remove matahari-*
Comment 10 James Antill 2013-04-16 19:47:30 UTC 
*** Bug 952760 has been marked as a duplicate of this bug. ***
Comment 11 Jan Zeleny 2013-04-22 12:48:14 UTC 
*** Bug 954330 has been marked as a duplicate of this bug. ***
Comment 12 Jan Zeleny 2013-05-24 09:40:42 UTC 
*** Bug 966763 has been marked as a duplicate of this bug. ***
Comment 13 Jan Zeleny 2013-06-04 06:47:53 UTC 
*** Bug 970439 has been marked as a duplicate of this bug. ***
Comment 14 Jan Zeleny 2013-07-24 06:12:10 UTC 
*** Bug 987564 has been marked as a duplicate of this bug. ***
Comment 15 Jan Zeleny 2013-07-24 06:14:29 UTC 
As per comment 9, this is not a bug in yum. Yum has no way of knowing that a package has been discontinued and it cannot uninstall packages on its own in case they block updates or anything. Closing the bug.
Comment 16 Jan Zeleny 2013-08-19 07:40:24 UTC 
*** Bug 998029 has been marked as a duplicate of this bug. ***
Comment 17 Jan Zeleny 2013-09-09 07:58:44 UTC 
*** Bug 1004964 has been marked as a duplicate of this bug. ***
Comment 18 Jan Zeleny 2013-09-19 10:23:27 UTC 
*** Bug 1009837 has been marked as a duplicate of this bug. ***
Comment 19 Jan Zeleny 2013-10-04 06:48:22 UTC 
*** Bug 1015195 has been marked as a duplicate of this bug. ***
Comment 20 Jan Zeleny 2013-12-06 13:15:15 UTC 
*** Bug 1039043 has been marked as a duplicate of this bug. ***
Comment 21 Jan Zeleny 2014-05-29 07:16:56 UTC 
*** Bug 1102280 has been marked as a duplicate of this bug. ***
Comment 22 Valentina Mukhamedzhanova 2014-09-03 12:38:16 UTC 
*** Bug 1117987 has been marked as a duplicate of this bug. ***
Comment 23 Jan Zeleny 2014-11-05 11:25:48 UTC 
*** Bug 1160231 has been marked as a duplicate of this bug. ***
Comment 24 Jan Zeleny 2015-01-23 16:59:43 UTC 
*** Bug 1185184 has been marked as a duplicate of this bug. ***
Comment 25 Jan Zeleny 2015-01-28 07:42:17 UTC 
*** Bug 1186552 has been marked as a duplicate of this bug. ***
Comment 26 Valentina Mukhamedzhanova 2016-07-25 15:47:35 UTC 
*** Bug 1320291 has been marked as a duplicate of this bug. ***
Comment 27 Valentina Mukhamedzhanova 2016-09-26 13:24:39 UTC 
*** Bug 1379364 has been marked as a duplicate of this bug. ***
Note You need to log in before you can comment on or make changes to this bug.