Bug 751834
Summary: | Hardcoded resource URL (ec2.amazonaws.com) | ||
---|---|---|---|
Product: | Red Hat Enterprise MRG | Reporter: | Luigi Toscano <ltoscano> |
Component: | condor-ec2-enhanced-hooks | Assignee: | Robert Rati <rrati> |
Status: | CLOSED ERRATA | QA Contact: | Luigi Toscano <ltoscano> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 2.1 | CC: | jneedle, matt, rrati |
Target Milestone: | 2.1.1 | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | condor-ec2-enhanced-hooks-1.3.0-1, condor-ec2-enhanced-1.3.0-1 | Doc Type: | Bug Fix |
Doc Text: |
C: EC2 Enhanced didn't allow setting a region
C: Using EC2 Enhanced with AMIs in a region other than a user's default region, so the job would fail to start
F: EC2 Enhanced now supports setting regions by adding 'EC2Region = "<region>"' to a job description file.
R: Running jobs on amis in regions us-east-1 and eu-west-1 succeeds
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2012-02-06 18:17:53 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: | 761165 | ||
Bug Blocks: | 756256, 765607 |
Description
Luigi Toscano
2011-11-07 17:55:28 UTC
You can now specify the region for ec2e by adding the following to your submit file: +EC2Region = "eu-west-1" Replace eu-west-1 with the region you ami is in. You can also set the availability zone by adding to your submit file: +EC2AvailabilityZone = "eu-west-1b" Fixed on branch: BZ751834-availability-zone 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: EC2 Enhanced didn't allow setting a region C: Using EC2 Enhanced with AMIs in a region other than a user's default region, so the job would fail to start F: EC2 Enhanced now supports setting regions by adding 'EC2Region = "<region>"' to a job description file. R: Running jobs on amis in different regions works The fix has a problem (RHEL5.7/RHEL6.2), JobRouterLog says: 01/18/12 20:54:21 TranslateClient::hookExited (src=13.0,route=Amazon small): Warning, hook /usr/libexec/condor/hooks/hook_translate.py (pid 12767) printed to stderr: Traceback (most recent call last): File "/usr/libexec/condor/hooks/hook_translate.py", line 438, in ? sys.exit(main()) File "/usr/libexec/condor/hooks/hook_translate.py", line 409, in main r_obj = AWSRegion.get_sqs_region(region) File "/usr/lib/python2.4/site-packages/condorec2e/region.py", line 26, in get_sqs_region return region_obj UnboundLocalError: local variable 'region_obj' referenced before assignment Initializing region_obj before the loop is enough to make it working. python-condorutils-1.5-4 condor-classads-7.6.5-0.12 condor-7.6.5-0.12 condor-ec2-enhanced-hooks-1.3.0-1 python-condorec2e-1.3.0-1 The region limitation comes from boto 1.7a, which only supports us-east-1 and eu-west-1. 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,4 @@ C: EC2 Enhanced didn't allow setting a region C: Using EC2 Enhanced with AMIs in a region other than a user's default region, so the job would fail to start F: EC2 Enhanced now supports setting regions by adding 'EC2Region = "<region>"' to a job description file. -R: Running jobs on amis in different regions works+R: Running jobs on amis in regions us-east-1 and eu-west-1 succeeds It is possible to specify other regions for EC2/Enhanced jobs (albeit limited to the ones supported by boto). Verified on RHEL5.7/6.2, i386/x86_64 (submitters). condor-7.6.5-0.12 condor-ec2-enhanced-hooks-1.3.0-1 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/RHSA-2012-0100.html |