Bug 806162

Summary: Scheduler sometimes leaves old recipe repos in /var/www/beaker/repos
Product: [Retired] Beaker Reporter: Dan Callaghan <dcallagh>
Component: schedulerAssignee: beaker-dev-list
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 0.8CC: bpeck, dcallagh, llim, mcsontos, rmancy, stl
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: Scheduler
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-09-19 23:05:38 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Dan Callaghan 2012-03-23 04:43:23 UTC
It seems the scheduler is not always cleaning up old recipe repos properly. On our Beaker instance we found 591 old repos under /var/www/beaker/repos dating from July 2010 to one week ago. They are "old" in the sense that the corresponding recipe is already completed, cancelled, or aborted, so the repo should no longer be present on disk.

Comment 2 Dan Callaghan 2012-03-23 04:47:48 UTC
A large number of the recipes in question were cancelled -- it is possible we are creating the repo and not destroying it, if the recipe is cancelled before it starts. (See also bug 715226.)

Comment 3 Nick Coghlan 2012-10-17 04:36:39 UTC
Bulk reassignment of issues as Bill has moved to another team.

Comment 5 Dan Callaghan 2013-09-19 23:05:38 UTC
I think with all the fixes for task repo generation and job status updating in recent Beaker releases, this issue should be fixed.

There are no orphaned repos in our production Beaker instance, aside from a handful from May 2013 (which pre-dates all those fixes).