Bug 609532 - VM Universe jobs that fail to exe get put on Hold
Summary: VM Universe jobs that fail to exe get put on Hold
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: condor
Version: 1.0
Hardware: All
OS: Linux
low
medium
Target Milestone: 2.0
: ---
Assignee: Timothy St. Clair
QA Contact: MRG Quality Engineering
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-30 14:16 UTC by Robert Rati
Modified: 2011-03-11 17:08 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-03-11 17:08:50 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

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
Note You need to log in before you can comment on or make changes to this bug.