Description of problem: S3-based images terminates when the AMI starts the shutdown. The default behavior for EBS-bases images is to stop when the AMI starts the shutdown. When this happen the jobs keeps running, and this breaks the assumption about the behavior of EC2 jobs. Therefore EC2 jobs should always force terminate-on-shutdown for AMIs instead of stop. Version-Release number of selected component (if applicable): condor-7.6.3-0.2
This must be from shutting down the instance internally, b/c the gahp only uses terminate calls. I'm guessing you are implying to set: InstanceInitiatedShutdownBehavior = terminate http://docs.amazonwebservices.com/AWSEC2/latest/APIReference/index.html?ApiReference-query-RunInstances.html
Yes, "InstanceInitiatedShutdownBehavior = terminate" should force the expected behavior.
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. New Contents: C: Starting an EC2 instance which is stored in EBS C: On shutdown the instance will go into stop, not terminate and the job will continue to run, and user will still be billed. F: Initialize instance to terminate on shutdown. R: Job will complete and instance will be terminated.
The feature has been implemented. Shutdown started from the AMI instance leads to instance termination (not stop). Verified on RHEL5.7/6.1, i386/x86_64 (submitter machines). condor-classads-7.6.3-0.3 condor-7.6.3-0.3
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHSA-2011-1249.html