Bug 725052
| Summary: | EC2E translate hook doesn't error if unable to read rsa public key | ||
|---|---|---|---|
| Product: | Red Hat Enterprise MRG | Reporter: | Robert Rati <rrati> |
| Component: | condor-ec2-enhanced-hooks | Assignee: | Robert Rati <rrati> |
| Status: | CLOSED ERRATA | QA Contact: | Luigi Toscano <ltoscano> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | medium | ||
| Version: | 1.3 | CC: | ltoscano, matt, mkudlej |
| Target Milestone: | 2.1 | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | condor-ec2-enhanced-hooks-1.2-4 | Doc Type: | Bug Fix |
| Doc Text: |
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.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-01-23 17:27:49 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 743350 | ||
|
Description
Robert Rati
2011-07-22 17:13:00 UTC
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 |