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):
Steps to Reproduce:
Are there any details on the HoldReason?
I don't recall the HoldReason. Likely a statement that the job could not run.
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).
Hold reason: Error from firstname.lastname@example.org: VMGAHP_ERR_INTERNAL