Bug 738423

Summary:	abort and cancel should ignore release_action failures
Product:	[Retired] Beaker	Reporter:	Bill Peck <bpeck>
Component:	scheduler	Assignee:	Bill Peck <bpeck>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	0.7	CC:	bpeck, dcallagh, mcsontos, rmancy, stl
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-10-06 03:35:27 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Bill Peck 2011-09-14 18:26:59 UTC

Description of problem:
We want to know if we can't power on or reboot a system when scheduling a job,  but I'm not sure we really care if we can't power off a system.

We ran into a problem where we couldn't abort or cancel a recipe in beaker because cobbler was mis-behaving.  We eventually fixed cobbler so it could be aborted but we shouldn't get stuck in a loop because of a bug in cobbler.

Version-Release number of selected component (if applicable):
0.7.01

How reproducible:
Put a bad profile on a system in cobbler

Comment 1 Raymond Mancy 2011-09-30 13:21:33 UTC

*** Bug 725620 has been marked as a duplicate of this bug. ***