Bug 433540 - debuginfo-install doesn't grab yum lock
debuginfo-install doesn't grab yum lock
Status: CLOSED UPSTREAM
Product: Fedora
Classification: Fedora
Component: yum-utils (Show other bugs)
8
All Linux
low Severity low
: ---
: ---
Assigned To: Seth Vidal
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2008-02-19 16:55 EST by Bradley
Modified: 2008-02-20 23:02 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-02-20 23:02:56 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Bradley 2008-02-19 16:55:25 EST
Description of problem:

A lockfile normally stops two yum instances running in parallel.
debuginfo-install doesn't grab this lock

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

yum-utils-1.1.11-1.fc8
yum-3.2.8-2.fc8

How reproducible: Always


Steps to Reproduce:
1. Run yum install <some large package>
2. While that runs, run debuginfo-install <some large package>
  
Actual results:

Both run simultaneously. When the second one goes to install, it pauses with:

warning: waiting for transaction lock on /var/lib/rpm/__db.000

Expected results: Second command pauses with:

Existing lock /var/run/yum.pid: another copy is running as pid 6402.
Another app is currently holding the yum lock; waiting for it to exit...

Additional info: Both runs were downloading the metadata at the same time,
although for different repos. Not sure if theres an extra lock stopping those
two downloads from clobbering each other
Comment 1 Seth Vidal 2008-02-20 23:02:56 EST
this is fixed in upstream and will be fixed in the next release of yum-utils, thanks

Note You need to log in before you can comment on or make changes to this bug.