Bug #14540
closed
[API] Limit number of container lock/unlock cycles
Added by Peter Amstutz about 6 years ago.
Updated almost 6 years ago.
Description
An un-runnable container can get stuck in an infinite loop of lock/unlock cycles (the dispatcher takes it, fails to start it, and the returns it to the queue). It should keep track of the number of times it is locked/unlocked and cancel the container if it exceeds a configured limit.
- Status changed from New to In Progress
- Status changed from In Progress to New
- Description updated (diff)
- Related to Bug #14495: [crunch2] include space required to download/unpack docker image in tmp disk request added
- Assigned To set to Lucas Di Pentima
- Assigned To deleted (
Lucas Di Pentima)
- Target version changed from 2018-12-12 Sprint to To Be Groomed
- Related to Bug #9688: [Crunch2] Limit number of dispatch attempts per container added
- Related to Bug #11561: [API] Limit number of lock/unlock cycles for a given container added
- Related to deleted (Bug #9688: [Crunch2] Limit number of dispatch attempts per container)
- Related to deleted (Bug #11561: [API] Limit number of lock/unlock cycles for a given container)
- Is duplicate of Bug #11561: [API] Limit number of lock/unlock cycles for a given container added
- Is duplicate of Bug #9688: [Crunch2] Limit number of dispatch attempts per container added
- Status changed from New to Duplicate
- Target version deleted (
To Be Groomed)
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by Tom Morris