Description of problem:
Certain job invocations could take too long and we want these to time out.
It would be nice if we could provide a default time out in the job template, and offer an option to override that timeout in the job invocation.
The timeout timer will start as soon as the job invocation starts, no need to actually measure the execution time on the client.
What is the expected behaviour when the timeout happens? Killing the job?
(In reply to Ivan Necas from comment #3)
> What is the expected behaviour when the timeout happens? Killing the job?
And also give reason why timed out (if possible)
Clearing needinfo as Pradeep replied
Created redmine issue http://projects.theforeman.org/issues/20016 from this bug
Upstream bug assigned to aruzicka
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/20016 has been resolved.
Verified on satellite-6.3.0-19.0.beta.el7sat.noarch, timeout option has been added and is applied correctly on remote hosts, see attached screenshots.
Created attachment 1334828 [details]
Created attachment 1334840 [details]
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.