Bug 609532

Summary:	VM Universe jobs that fail to exe get put on Hold
Product:	Red Hat Enterprise MRG	Reporter:	Robert Rati <rrati>
Component:	condor	Assignee:	Timothy St. Clair <tstclair>
Status:	CLOSED NOTABUG	QA Contact:	MRG Quality Engineering <mrgqe-bugs>
Severity:	medium	Docs Contact:
Priority:	low
Version:	1.0	CC:	iboverma, ltoscano, matt
Target Milestone:	2.0
Target Release:	---
Hardware:	All
OS:	Linux
URL:
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-03-11 17:08:50 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 Robert Rati 2010-06-30 14:16:29 UTC

Description of problem:
VM Universe jobs that have problems executing get put on Hold with a HoldReason set.  A failure to run on one machine does not mean it would fail to execute on another VM capable execute node.  VM Universe jobs that fail to run should be placed back in Idle state rather than on Hold.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Timothy St. Clair 2011-02-17 21:15:04 UTC

Are there any details on the HoldReason?

Comment 2 Robert Rati 2011-02-17 22:06:39 UTC

I don't recall the HoldReason.  Likely a statement that the job could not run.

Comment 4 Timothy St. Clair 2011-03-11 17:08:50 UTC

So in looking through the code, this is expected behavior if the job outright fails to execute with some error (usually due to some botched submission or configuration).

e.g.

Hold reason: Error from slot1.com: VMGAHP_ERR_INTERNAL