Bug 1307098
Summary: | yum downloadonly does not reliably remove lock files | |||
---|---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Andy Grimm <agrimm> | |
Component: | yum | Assignee: | Valentina Mukhamedzhanova <vmukhame> | |
Status: | CLOSED ERRATA | QA Contact: | Eva Mrakova <emrakova> | |
Severity: | urgent | Docs Contact: | ||
Priority: | urgent | |||
Version: | 6.7 | CC: | emrakova, james.antill, jgoulding, ksrot, mkolaja, twiest | |
Target Milestone: | rc | Keywords: | Patch, ZStream | |
Target Release: | 6.8 | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | yum-3.2.29-74.el6 | Doc Type: | Bug Fix | |
Doc Text: |
Previously, a /var/run/yum.pid file was left on the disk after running the "yum --downloadonly" command. Consequently, under certain circumstances, the
"yum" command failed because the yum utility incorrectly assumed that another instance of "yum" was already running. With this update, /var/run/yum.pid is correctly removed after running "yum --downloadonly", and the described problem
no longer occurs.
|
Story Points: | --- | |
Clone Of: | ||||
: | 1337912 (view as bug list) | Environment: | ||
Last Closed: | 2017-03-21 11:00:55 UTC | Type: | Bug | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | ||||
Bug Blocks: | 1269194, 1277547, 1337912 |
Description
Andy Grimm
2016-02-12 17:16:17 UTC
One update on this: I realized that I may be wrong about the current function/purpose of the /var/lib/rpm/__db* files. I was under the impression that those were lock files that would block subsequent transactions, but that does not seem to be the case in further tests. Also, it seems that while calling self.closeRpmDB() does close those filehandles, it doesn't actually remove the files. Adding self.doUnlock() prior to the sys.exit definitely works to remove the PID file, though. It looks like upstream code closes these database well before the exit. It appears to have been added in this commit: http://yum.baseurl.org/gitweb?p=yum.git;a=commitdiff;h=05666dc9295fb433d1b081068dbe74e535cfc228 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-2017-0702.html |