Actions
Bug #14540
closed
[API] Limit number of container lock/unlock cycles
Status:
Duplicate
Priority:
Normal
Assigned To:
-
Category:
-
Target version:
-
Story points:
-
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.
Related issues
Updated by Peter Amstutz over 5 years ago
- Status changed from New to In Progress
Updated by Peter Amstutz over 5 years ago
- Status changed from In Progress to New
- Description updated (diff)
Updated by Peter Amstutz over 5 years ago
- Related to Bug #14495: [crunch2] include space required to download/unpack docker image in tmp disk request added
Updated by Lucas Di Pentima over 5 years ago
- Assigned To set to Lucas Di Pentima
Updated by Lucas Di Pentima over 5 years ago
- Assigned To deleted (
Lucas Di Pentima) - Target version changed from 2018-12-12 Sprint to To Be Groomed
Updated by Tom Morris over 5 years ago
- Related to Bug #9688: [Crunch2] Limit number of dispatch attempts per container added
Updated by Tom Morris over 5 years ago
- Related to Bug #11561: [API] Limit number of lock/unlock cycles for a given container added
Updated by Peter Amstutz over 5 years ago
- Related to deleted (Bug #9688: [Crunch2] Limit number of dispatch attempts per container)
Updated by Peter Amstutz over 5 years ago
- Related to deleted (Bug #11561: [API] Limit number of lock/unlock cycles for a given container)
Updated by Peter Amstutz over 5 years ago
- Is duplicate of Bug #11561: [API] Limit number of lock/unlock cycles for a given container added
Updated by Peter Amstutz over 5 years ago
- Is duplicate of Bug #9688: [Crunch2] Limit number of dispatch attempts per container added
Actions