Feature #8159
As a system I want the application of remote commands to retry on failure on a per system basis
| Status: | New | ||
|---|---|---|---|
| Priority: | Normal | ||
| Assignee: |  David Caplan | ||
| Category: | - | ||
| Target version: | - | ||
| Difficulty: | Team Backlog: | ||
| Triaged: | Fixed in Releases: | ||
| Bugzilla link: | Found in Releases: | ||
| Pull request: | |||
Description
Ideally the aggressiveness of the retry algorithm should be tunable as meta-data that accompanies a given remote execution script/template. I am imagining the ability to set a value between 1 and 5, 1 meaning no retry, 5 meaning continual retry until success. The intermediate choices will eventually give up.
Related issues
History
#1
Updated by David Caplan over 3 years ago
- Blocks Tracker #8121: Remote Execution Tracker added
#2
Updated by Dominic Cleal about 2 years ago
- Project changed from Foreman to Foreman Remote Execution
#3
Updated by Marek Hulán about 2 years ago
- Related to Bug #11361: Ability to set retry count and interval and timouts for the job added
#4
Updated by Marek Hulán about 2 years ago
- Blocks deleted (Tracker #8121: Remote Execution Tracker)