Bug 861251

Summary: please backport YUM’s --setopt=exit_on_lock=true feature
Product: Red Hat Enterprise Linux 6 Reporter: Christoph Anton Mitterer <calestyo>
Component: yumAssignee: Packaging Maintenance Team <packaging-team-maint>
Status: CLOSED NOTABUG QA Contact: BaseOS QE Security Team <qe-baseos-security>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.3CC: ddumas, james.antill
Target Milestone: rcKeywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-04-15 20:52:27 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:

Description Christoph Anton Mitterer 2012-09-27 23:35:03 UTC 
Hi.

I'm currently maintaining check_yum[0] which is THE Nagios/Icinga check for the YUM package update status.

A rather important feature of check_yum is its "--no-warn-on-lock" option, which makes that invocations of check_yum that fail (due to an already running/blocking YUM) are ignored.
Otherwise one would get many false positives.

Now the thing is that (since some time?) YUM blocks, when another YUM process is already running (which is undesired for check_yum, as it will run into a timeout, which must be considered an error).

Now recent yum versions support a feature (--setopt=exit_on_lock=true) which makes YUM exit, when the lock cannot be gained.

In a thread[1] on yum-devel, James Antill suggested me that it should be very easy to backport that feature for RHEL5 and that I should ask here for it.


Thanks,
Chris.



[0] https://code.google.com/p/check-yum/
[1] http://lists.baseurl.org/pipermail/yum-devel/2012-September/009641.html
Comment 2 James Antill 2013-04-15 20:52:27 UTC 
 RHEL-6 already has exit_on_lock, RHEL-5 is unlikely to get any backported features at this point.