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):
Steps to Reproduce:
1. yum check
yum check operation takes extremely long time.
yum check operation takes less time or yum check provides user a operation status 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>
Please note -d 9 or --verbose swithes do not bring more light into what yum is actually doing.
Created attachment 933689 [details]
packed /var/lib/rpm rpm databases (from RHEL 6.5 i686)
Same behavior seen on older yum& rpm as well (RHEL 6.4)
# rpm -q yum rpm
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
# time yum check
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.
Author: James Antill <email@example.com>
Date: Mon Jun 2 13:04:03 2014 -0400
Have check provides check directly against the rpm index, and then quit.
Probably the easiest way to see if that's the problem is to git clone the upstream code, and run: ./yummain.py check
Created attachment 967216 [details]
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.