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 590675 - Lock yum for non-root users, so multiple simultaneous runs don't interact badly
Summary: Lock yum for non-root users, so multiple simultaneous runs don't interact badly
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: yum
Version: 6.1
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: James Antill
QA Contact: Karel Srot
URL:
Whiteboard: abrt_hash:1ed0db48
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-10 13:14 UTC by Ben Woodard
Modified: 2014-01-21 06:17 UTC (History)
1 user (show)

Fixed In Version: yum-3.2.29-1.el6
Doc Type: Bug Fix
Doc Text:
Cause: yum only had a lock for root, in /var/run Consequence: you could two instances of yum at once as non-root Fix: yum now also locks the cache. Result: You can run two instances, but the second will wait for the lock
Clone Of:
Environment:
Last Closed: 2011-05-19 13:33:19 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
File: backtrace (3.08 KB, text/plain)
2010-05-10 13:14 UTC, Ben Woodard 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:0602 0 normal SHIPPED_LIVE yum bug fix and enhancement update 2011-05-19 09:37:29 UTC

Description Ben Woodard 2010-05-10 13:14:42 UTC 
abrt 1.1.0 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/bin/python /usr/bin/yumdownloader --disablerepo=* --enablerepo=*-debug* --quiet keyutils-debuginfo-1.4-1.el6.x86_64
component: yum-utils
executable: /usr/bin/yumdownloader
kernel: 2.6.32-23.el6.x86_64
package: yum-utils-1.1.26-7.el6
reason: yumRepo.py:1053:_revertOldRepoXML:OSError: [Errno 2] No such file or directory
release: Red Hat Enterprise Linux release 6.0 Beta (Santiago)

How to reproduce
-----
1. Just downloading today's update
Comment 1 Ben Woodard 2010-05-10 13:14:44 UTC 
Created attachment 412833 [details]
File: backtrace
Comment 3 RHEL Program Management 2010-05-10 14:32:16 UTC 
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.
Comment 4 James Antill 2010-05-20 19:22:15 UTC 
You were running this as a normal user?

Was anything else happening at the time?
Comment 5 James Antill 2010-05-25 16:31:10 UTC 
If it's the problem I think it is (non-root users need some kind of lock), we can probably do it for 6.1
Comment 11 James Antill 2011-02-18 14:54:52 UTC 
Yeh, the easiest way to test involves keeping old metadata around for a repo.

You can just test that the new yum has locking, but opening two terminals and running "yum search yum" in both of them ... if one of them doesn't start printing the "yum is locked" data, then there is no lock.
Comment 12 Karel Srot 2011-02-18 15:20:29 UTC 
> You can just test that the new yum has locking...

Thats the way I have tested bug 669746. But the traceback is a bit different, therefore I am also trying to reproduce the one in #c0. I will try it again with the old metadata.
Comment 14 James Antill 2011-05-12 19:03:29 UTC 
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Cause: yum only had a lock for root, in /var/run
Consequence: you could two instances of yum at once as non-root
Fix: yum now also locks the cache.
Result: You can run two instances, but the second will wait for the lock
Comment 15 errata-xmlrpc 2011-05-19 13:33:19 UTC 
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2011-0602.html
Note You need to log in before you can comment on or make changes to this bug.