Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionDaniel Lobato Garcia
2016-10-18 14:25:23 UTC
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?
Comment 4Pradeep Kumar Surisetty
2017-04-18 15:26:24 UTC
(In reply to Ivan Necas from comment #3)
> What is the expected behaviour when the timeout happens? Killing the job?
yes
And also give reason why timed out (if possible)
Comment 5Daniel Lobato Garcia
2017-05-26 14:56:14 UTC
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.
https://access.redhat.com/errata/RHSA-2018:0336