Bug 1428234 - Missing AWS Regions
Summary: Missing AWS Regions
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Providers
Version: 5.7.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: GA
: 5.8.0
Assignee: Marcel Hild
QA Contact: Matouš Mojžíš
URL:
Whiteboard: ec2:provider
Depends On:
Blocks: 1432960
TreeView+ depends on / blocked
 
Reported: 2017-03-02 05:45 UTC by Greg Jones
Modified: 2018-04-16 16:52 UTC (History)
9 users (show)

Fixed In Version: 5.8.0.6
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1432960 (view as bug list)
Environment:
Last Closed: 2017-06-12 16:17:18 UTC
Category: Feature
Cloudforms Team: CFME Core
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Screenshot (48.80 KB, image/png)
2017-03-02 05:45 UTC, Greg Jones
no flags Details

Description Greg Jones 2017-03-02 05:45:52 UTC
Created attachment 1258995 [details]
Screenshot

Description of problem:

Missing AWS Regions


Version-Release number of selected component (if applicable):

5.7.1.3

How reproducible:

100%

Steps to Reproduce:
1. Add New Cloud Provider
2. Select Amazon EC2 provider Type
3. Activate Region Dropdown

Actual results:
Current Regions:

ap-northeast-1
ap-northeast-2
ap-southeast-1
ap-southeast-2
eu-central-1
eu-west-1
sa-east-1
us-west-1
us-west-2
us-east-1
us-east-2


Expected results:

% aws ec2 describe-regions
{
    "Regions": [
        {
            "Endpoint": "ec2.ap-south-1.amazonaws.com", 
            "RegionName": "ap-south-1"
        }, 
        {
            "Endpoint": "ec2.eu-west-2.amazonaws.com", 
            "RegionName": "eu-west-2"
        }, 
        {
            "Endpoint": "ec2.eu-west-1.amazonaws.com", 
            "RegionName": "eu-west-1"
        }, 
        {
            "Endpoint": "ec2.ap-northeast-2.amazonaws.com", 
            "RegionName": "ap-northeast-2"
        }, 
        {
            "Endpoint": "ec2.ap-northeast-1.amazonaws.com", 
            "RegionName": "ap-northeast-1"
        }, 
        {
            "Endpoint": "ec2.sa-east-1.amazonaws.com", 
            "RegionName": "sa-east-1"
        }, 
        {
            "Endpoint": "ec2.ca-central-1.amazonaws.com", 
            "RegionName": "ca-central-1"
        }, 
        {
            "Endpoint": "ec2.ap-southeast-1.amazonaws.com", 
            "RegionName": "ap-southeast-1"
        }, 
        {
            "Endpoint": "ec2.ap-southeast-2.amazonaws.com", 
            "RegionName": "ap-southeast-2"
        }, 
        {
            "Endpoint": "ec2.eu-central-1.amazonaws.com", 
            "RegionName": "eu-central-1"
        }, 
        {
            "Endpoint": "ec2.us-east-1.amazonaws.com", 
            "RegionName": "us-east-1"
        }, 
        {
            "Endpoint": "ec2.us-east-2.amazonaws.com", 
            "RegionName": "us-east-2"
        }, 
        {
            "Endpoint": "ec2.us-west-1.amazonaws.com", 
            "RegionName": "us-west-1"
        }, 
        {
            "Endpoint": "ec2.us-west-2.amazonaws.com", 
            "RegionName": "us-west-2"
        }
    ]
}



Additional info:

Comment 2 Greg Jones 2017-03-02 19:13:38 UTC
I see this is targeted for 5.7.2

Is there a workaround in the meantime?

Comment 3 Marcel Hild 2017-03-03 13:45:52 UTC
No workaround per settings. You can edit the regions ruby file, but this it not supported

Comment 5 Marcel Hild 2017-03-13 19:55:23 UTC
yeah, the linked BZ is for

Comment 8 Matouš Mojžíš 2017-04-10 08:39:31 UTC
Verified in 5.8.0.9. I could add eu-west-2 London and ap-south-1 Mombai providers to CFME.


Note You need to log in before you can comment on or make changes to this bug.