Bug 1349423

Summary: Dynamic Dropdown list of AWS instance Type for AWS GovCloud seems to be returning instance types that are not supported by AWS GovCloud
Product: Red Hat CloudForms Management Engine Reporter: John Prause <jprause>
Component: ProvidersAssignee: Marcel Hild <mhild>
Status: CLOSED ERRATA QA Contact: Jeff Teehan <jteehan>
Severity: high Docs Contact:
Priority: high    
Version: 5.5.0CC: carnott, cpelland, gblomqui, jdeubel, jfrey, jhardy, jocarter, jteehan, mfeifer, mhild, mmojzis, obarenbo, rmoore, simaishi, ssainkar, thenness
Target Milestone: GAKeywords: ZStream
Target Release: 5.6.2   
Hardware: x86_64   
OS: Linux   
Whiteboard: ui:ec2
Fixed In Version: 5.6.2.0 Doc Type: Bug Fix
Doc Text:
Previously, dynamic dropdown list of instance types for AWS GovCloud was returning instance types that are not supported by AWS GovCloud. This was because many of the instance type 'flavors' that are not actually available in AWS GovCloud (eg,m4.large) returned into VMDB which were presented in the dropdown list. This fix removed GovCloud from AWS list of regions which has resolved the issue.
Story Points: ---
Clone Of: 1346065 Environment:
Last Closed: 2016-10-04 14:28:31 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: AWS Target Upstream Version:
Embargoed:
Bug Depends On: 1346065    
Bug Blocks:    

Comment 3 Marcel Hild 2016-09-08 16:01:44 UTC
darga PR merged at https://github.com/ManageIQ/manageiq/pull/10902

Comment 4 Jeff Teehan 2016-09-26 20:08:59 UTC
This works as described as far as removing regions from the list.  Moving to verified.  This is what amazon says about it, so I guess we're in line with that.

The following table lists the regions provided by an AWS account. Note that you can't describe or access additional regions from an AWS account, such as AWS GovCloud (US) or China (Beijing).

Comment 5 Jeff Teehan 2016-09-26 22:37:15 UTC
I don't think we need a test case for this.

Comment 7 errata-xmlrpc 2016-10-04 14:28:31 UTC
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.

https://rhn.redhat.com/errata/RHSA-2016-1996.html