Description of problem: If the RSA public key is defined, but to an invalid file, then the translate hook will run successfully but result in jobs that can never be run in EC2. What's worse, there's no indication this is the problem, causing debugging headaches. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
In addition to verifying that the file exists, the translate hook will now also verify the rsa key, access key, and seceret access key files are readable. Fixed on: BZ725052-report-bad-rsapublickey
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: Configuring an invalid RSA public key file in an EC2 Enhanced route C: No error message is given about the invalid public key and the job would be routed to EC2 but never be able to run. F: An error message will be produced. R: Invalid RSA key in an EC2 Enhanced route will produce an error message in the logs and the job will not be routed to EC2.
Technical note updated. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1,4 +1 @@ -C: Configuring an invalid RSA public key file in an EC2 Enhanced route +When an invalid RSA public key file was configured in an EC2 Enhanced route, no error message was given about the invalid public key, the job was routed to EC2 but was never be able to run. This bug has been fixed, an error message is now returned, and the job is not routed to EC2 in the described scenario.-C: No error message is given about the invalid public key and the job would be routed to EC2 but never be able to run. -F: An error message will be produced. -R: Invalid RSA key in an EC2 Enhanced route will produce an error message in the logs and the job will not be routed to EC2.
Availability of RSA public key, of secret and access key files is properly checked now by the translator hook and the job is not routed anymore if the files are not available/accessible. Verified on RHEL5.7/6.2, i386/x86_64. condor-7.6.5-0.8 condor-classads-7.6.5-0.8 condor-ec2-enhanced-hooks-1.2-4.el6.noarch python-condorec2e-1.2-4.el6.noarch
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHEA-2012-0045.html