Project

General

Profile

Actions

Bug #37498

closed

The 'Timeout to kill' setting is not honored while running remote execution jobs in Satellite

Added by Adam Ruzicka 6 months ago. Updated 5 months ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Difficulty:
Triaged:
No
Found in Releases:

Description

The 'Timeout to kill' setting is not honored while running remote execution jobs

Steps to Reproduce:
1. Configure remote execution in Satellite (preferable Push Mode)
2. Navigate to Satellite WebUI -> Monitor -> Jobs -> Run Job
3. Ensure there is some value set for "Timeout to kill" (say '5')

Actual results: The "Timeout to kill" setting is not honored and the job is not killed after 5 seconds

Expected results: The remote execution job should be killed within 5 seconds

Actions #1

Updated by The Foreman Bot 6 months ago

  • Status changed from New to Ready For Testing
  • Assignee set to Adam Ruzicka
  • Pull request https://github.com/theforeman/smart_proxy_remote_execution_ssh/pull/115 added
Actions #2

Updated by The Foreman Bot 5 months ago

  • Fixed in Releases smart_proxy_remote_execution_ssh-0.10.5 added
Actions #3

Updated by Adam Ruzicka 5 months ago

  • Status changed from Ready For Testing to Closed
Actions #4

Updated by Adam Ruzicka 5 months ago

  • Fixed in Releases smart_proxy_remote_execution_ssh-0.10.6 added
  • Fixed in Releases deleted (smart_proxy_remote_execution_ssh-0.10.5)
Actions

Also available in: Atom PDF