Bug 1386278 – [RFE] Job invocations should timeout

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1386278 - [RFE] Job invocations should timeout

Summary:	[RFE] Job invocations should timeout

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Satellite 6
Classification:	Red Hat
Component:	Remote Execution (Show other bugs)
Sub Component:
Version:	6.1.9
Hardware:	x86_64 All

Priority	high Severity high (vote)
Target Milestone:	Beta
Target Release:	Unused
Assigned To:	Adam Ruzicka
QA Contact:	Peter Ondrejka
Docs Contact:

URL:
Whiteboard:
Keywords:	FieldEngineering, FutureFeature, PrioBumpGSS, Triaged

Depends On:
Blocks:	1479962
	Show dependency tree / graph

Reported:	2016-10-18 10:25 EDT by Daniel Lobato Garcia
Modified:	2018-08-31 11 EDT (History)
CC List:	12 users (show)

See Also:
Fixed In Version:	tfm-rubygem-foreman_remote_execution-1.3.2
Doc Type:	If docs needed, set a value
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2018-02-21 07:36:49 EST
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
screenshot (55.81 KB, image/png) 2017-10-05 09:35 EDT, Peter Ondrejka	no flags	Details
screenshot-execution (53.43 KB, image/png) 2017-10-05 09:36 EDT, Peter Ondrejka	no flags	Details
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Foreman Issue Tracker	20016	None	None	None	2017-06-14 06:50 EDT
Red Hat Product Errata	RHSA-2018:0336	normal	SHIPPED_LIVE	Important: Satellite 6.3 security, bug fix, and enhancement update	2018-02-21 17:43:42 EST

Groups: None (edit)

Description Daniel Lobato Garcia 2016-10-18 10:25:23 EDT

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.

Comment 3 Ivan Necas 2017-04-18 11:15:38 EDT

What is the expected behaviour when the timeout happens? Killing the job?

Comment 4 Pradeep Kumar Surisetty 2017-04-18 11:26:24 EDT

(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 5 Daniel Lobato Garcia 2017-05-26 10:56:14 EDT

Clearing needinfo as Pradeep replied

Comment 6 Adam Ruzicka 2017-06-14 06:50:55 EDT

Created redmine issue http://projects.theforeman.org/issues/20016 from this bug

Comment 7 pm-sat@redhat.com 2017-06-14 08:13:46 EDT

Upstream bug assigned to aruzicka@redhat.com

Comment 8 pm-sat@redhat.com 2017-06-14 08:13:51 EDT

Upstream bug assigned to aruzicka@redhat.com

Comment 10 pm-sat@redhat.com 2017-07-11 10:12:27 EDT

Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/20016 has been resolved.

Comment 11 pm-sat@redhat.com 2017-07-26 10:12:40 EDT

Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/20016 has been resolved.

Comment 14 Peter Ondrejka 2017-10-05 09:35:11 EDT

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.

Comment 15 Peter Ondrejka 2017-10-05 09:35 EDT

Created attachment 1334828 [details]
screenshot

Comment 16 Peter Ondrejka 2017-10-05 09:36 EDT

Created attachment 1334840 [details]
screenshot-execution

Comment 19 errata-xmlrpc 2018-02-21 07:36:49 EST

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

Note You need to log in before you can comment on or make changes to this bug.