Description of problem:
If you have a bad submission file you can cause an instance to run indefinitely without any return information
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.) In your submission file specify some custom script
executable = /tmp/my_script.sh
2.) Set should_transfer_files = no (when it should be yes)
Job will run forever.
Job should fail with some information for the user.
Added the following parameters that give additional information about the job in the AMI:
The EC2HookArg can be one of the following values (The meaning follows):
2 - Job was accepted
3 - Job was rejected
5 - Job exited normally
6 - Job was removed
7 - Job was held
8 - Job was evicted
EC2LastFailureReason will be set in a failure case to a string with an explanation
EC2JobStatus is the status of the job running on the condor in the AMI
The above parameters can be used in policy expressions, but nothing will be done with the job automatically. It is not possible for EC2E to place a job on hold by itself.
Tracking on branch:
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
C: An EC2 Enhanced job failed to run in the AMI
C: It was difficult to know what happened when the job ran in EC2
F: The following attributes were added to give additional insight into what occurred in the AMI: EC2JobStatus, EC2LastFailureReason, EC2HookArg
R: Additional feedback of the job status in the AMI is available
MRG-G is in maintenance only and only customer escalations will be addressed from this point forward. This issue can be re-opened if a customer escalation associated with this issue occurs.