Bug 853497 - [BUG] beaker-expire-distros needs locking
Summary: [BUG] beaker-expire-distros needs locking
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Beaker
Classification: Retired
Component: lab controller
Version: 0.9
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Dan Callaghan
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-08-31 18:13 UTC by Bill Peck
Modified: 2019-05-22 13:43 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-10-11 23:50:37 UTC
Embargoed:

Attachments (Terms of Use)

Description Bill Peck 2012-08-31 18:13:52 UTC 
Description of problem:

beaker-expire-distros needs to verify its not already running before starting.

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

How reproducible:
Unknown
Comment 1 Dan Callaghan 2012-09-03 00:55:11 UTC 
I think this should be the responsibility of whoever is invoking beaker-expire-distros, e.g. the cron job if that's what the site is using.

Doesn't cron already have support for preventing the same job running concurrently?
Comment 2 Dan Callaghan 2012-09-03 01:31:17 UTC 
(In reply to comment #1)
> Doesn't cron already have support for preventing the same job running
> concurrently?

It seems not. But we can very easily add some locking to the cron job which we ship.
Comment 3 Dan Callaghan 2012-09-03 05:29:57 UTC 
On Gerrit: http://gerrit.beaker-project.org/1315
Comment 5 Dan Callaghan 2012-10-11 23:50:37 UTC 
Beaker 0.9.4 has been released.
Note You need to log in before you can comment on or make changes to this bug.