Project

General

Profile

Actions

Bug #11361

closed

Ability to set retry count and interval and timouts for the job

Added by Ivan Necas over 9 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Related issues 4 (2 open2 closed)

Related to Foreman Remote Execution - Feature #10750: Job cancelling supportClosed06/09/201507/15/2015Actions
Related to Foreman Remote Execution - Bug #11362: Better error handling of errors in foreman - smart proxy communicationNew08/14/2015Actions
Related to Foreman Remote Execution - Bug #11963: Getting routing error just after execution startClosedMarek Hulán09/25/2015Actions
Related to Foreman Remote Execution - Feature #8159: As a system I want the application of remote commands to retry on failure on a per system basisNewDavid Caplan10/29/2014Actions
Actions #1

Updated by Ivan Necas over 9 years ago

Actions #2

Updated by Ivan Necas over 9 years ago

  • Related to Bug #11362: Better error handling of errors in foreman - smart proxy communication added
Actions #3

Updated by Marek Hulán about 9 years ago

  • Target version set to 85
Actions #4

Updated by The Foreman Bot about 9 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/foreman_remote_execution/pull/34 added
  • Pull request deleted ()
Actions #5

Updated by Marek Hulán about 9 years ago

  • Related to Bug #11963: Getting routing error just after execution start added
Actions #6

Updated by Marek Hulán about 9 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100
  • Translation missing: en.field_release set to 95
Actions #7

Updated by Marek Hulán over 8 years ago

  • Related to Feature #8159: As a system I want the application of remote commands to retry on failure on a per system basis added
Actions

Also available in: Atom PDF