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.
+++ This bug was initially created as a clone of Bug #815568 +++
Description of problem:
yum --security check-update -C does not work for a non-root userm even if it was preceded by yum makecache was as root user.
Version-Release number of selected component (if applicable):
yum-3.4.3-47.el7.noarch
How reproducible:
always
Steps to Reproduce:
1. Make sure that there is a new security update in a repo
2. As root prepare the cache
# yum makecache
3. As non-root user check is the security update is reported
$ yum --security check-update -C
Actual results:
Loaded plugins: product-id, security, subscription-manager
Error: Cannot access repository dir /var/tmp/yum-bz815568-i67Q5h/x86_64/6.92Server/bz815568
Expected results:
Loaded plugins: downloadonly, fastestmirror, product-id, security, subscription-
: manager, tmprepo
Not root, certificate-based repositories not updated
Limiting package lists to security relevant ones
1 package(s) needed for security, out of 4 available
bz815568-test.noarch 1.0-2 bz815568
> yum --security check-update -C does not work for a non-root userm even if it was preceded by yum makecache was as root user.
Pretty sure this is just generic fallout from the "users and non-root users are completely separate" change. In the above case we don't even have a cachedir for the user.
In RHEL-6 and previous -C as a user would use the root cachedir ... which is better in the above case, but falls down when root hasn't run makecache recently (at which point there's no way for the user to recover).
Implementing and testing this feature is actually quite easy, but it changes Yum bahavior in often used code paths (but only when -C option was specified, that's the one good thing), so it's possible it'll break other tests or use cases.
Anyway, I've implemented this in yum-3.4.3-102.fc20, and CAN move it to .el7 easily if QA can test it.
Yes, it's commited. The bug has been fixed in rhel7.0 with a rebase I did on Jul 30 2013. The fix is also in Fedora since Jul 18 2013. AFAIK there were no regressions reported.
Testing the feature itself is probable easy- see Patrik's steps to reproduce. Or, use a simple reproducer like this:
1) $ yum clean all (drop the user cache)
2) # yum makecache (popullate the root cache)
3) $ yum --cacheonly info yum (access the empty user cache cacheonly)
The step 3 should proceed with no failure and no metadata download.
Karel, could you reconsider the nak, please?
This request was resolved in Red Hat Enterprise Linux 7.0.
Contact your manager or support representative in case you have further questions about the request.