Description of problem: Our documentation states that WantAWS=!=true should be specified in the job submission file for the job to be correctly routed to JobRouter when stard runs on the node (see rhbz513046). Unfortunately with this setup the routed job does not terminate correctly; according to developers, EC2 hooks should be changed to set WantAWS = False in the classad put in SQS. Version-Release number of selected component (if applicable): Reproduced on MRG 2.0 rc: condor-7.6.1-0.8 condor-ec2-enhanced-hooks-1.2-2 but the issue should also be in 1.3.
'WantAWS = False' is set in the classad sent to sqs Fixed on BZ710215-set-WantAWS
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: Following documentation to ensure an EC2E job was routed only to EC2 C: The job would route to EC2, but would never run to completion F: Set WantEC2E = False in the ClassAd sent to the EC2 AMI R: EC2E jobs that include WantAWS =!= True in their requirements will run.
WantAWS is now set to False by the hooks and jobs terminates correctly. Verified on RHEL5.7/6.1, i386/x86_64 (submitters). condor-7.6.3-0.3 condor-classads-7.6.3-0.3 python-condorutils-1.5-4 condor-job-hooks-1.5-4 python-condorec2e-1.2-3 condor-ec2-enhanced-hooks-1.2-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