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.
DescriptionFrantisek Reznicek
2014-09-02 07:51:09 UTC
Description of problem:
yum check hangs.
When I tried multiple times on multiple machines RHEL 6.5 / 6.6 Server i686 / x86_64 (some KVM, some bare metal) I realized yum check is not moving forward and taking much more time than I expected for all of them (5 machines). There was no other yum running, machines were not subscribed to RHN, there was no network problem as installation was working as expected.
Average yum check execution was over 10 minutes (5 machines).
Users are not going to be happy with this behavior as there is no information about progress atm.
If yum check is going to take more time (as there are new operations added) then users need to be aware yum check is doing the work not just hanging.
Version-Release number of selected component (if applicable):
yum-3.2.29-43.el6_5.noarch
yum-3.2.29-60.el6.noarch
How reproducible:
100%
Steps to Reproduce:
1. yum check
Actual results:
yum check operation takes extremely long time.
Expected results:
yum check operation takes less time or yum check provides user a operation status info.
Additional info:
# yum check
Loaded plugins: auto-update-debuginfo, product-id, security, subscription-manager
This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register.
<hang for >8 minutes>
check all
#
Comment 2Frantisek Reznicek
2014-09-02 08:41:59 UTC
Please note -d 9 or --verbose swithes do not bring more light into what yum is actually doing.
Comment 5Frantisek Reznicek
2014-09-02 10:38:45 UTC
Comment 7Frantisek Reznicek
2014-09-02 11:05:31 UTC
Same behavior seen on older yum& rpm as well (RHEL 6.4)
# rpm -q yum rpm
yum-3.2.29-40.el6.noarch
rpm-4.8.0-37.el6.x86_64
Comment 8Frantisek Reznicek
2014-09-02 11:39:42 UTC
My initial thought was that something changed recently which is not correct as same behavior is reproducible on RHEL 6.1 x86_64:
# rpm -q yum rpm
yum-3.2.29-17.el6.noarch
rpm-4.8.0-16.el6_1.1.x86_64
# time yum check
check all
real 9m31.613s
user 8m39.071s
sys 0m51.106s
Is it "check provides" that's the problem? Do you have a lot of kernel-debug packages installed or something? Basically what does:
rpm -qa --provides | wc -l
...say? We had an upstream "fix" for this a bit ago, we could backport that fairly easily.
commit 406fbca7d1020fcf6c9d3d98c02bf8198ea90d57
Author: James Antill <james>
Date: Mon Jun 2 13:04:03 2014 -0400
Have check provides check directly against the rpm index, and then quit.
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://rhn.redhat.com/errata/RHBA-2015-1384.html