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.

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

 RHEL-6 already has exit_on_lock, RHEL-5 is unlikely to get any backported features at this point.