Bug 1362379

Summary:	Restart the machine when the job is aborted
Product:	[Community] GlusterFS	Reporter:	Nigel Babu <nigelb>
Component:	project-infrastructure	Assignee:	Nigel Babu <nigelb>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs, gluster-infra
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-01-31 05:24:00 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Nigel Babu 2016-08-02 05:47:35 UTC

When a job is aborted, it leaves a bunch of remaining gluster processes. The safest thing to do is to reboot the machine automatically when a job is aborted.

Comment 1 Nigel Babu 2016-09-26 05:48:27 UTC

Note: A good way to do this would be to use a publisher like we do for Centos CI jobs.

Comment 2 Nigel Babu 2017-01-31 05:24:00 UTC

We've got this sorted for NetBSD now. The majority of the use case has been for NetBSD, so we'll close this now.