Description of problem: Customer Reports that dynamic dropdown list of instance types for AWS GovCloud is presenting instance-types not supported by AWS GovCloud and believes this is a CFME error Version-Release number of selected component (if applicable):5.5.3.4 How reproducible: needs a connection to AWS GovCloud, not sure we can reproduce this in house. Steps to Reproduce: 1. 2. 3. Actual results: List of instance types returned into VMDB follows: ===== [----] I, [2016-06-13T06:22:05.141750 #3313:46a5384] INFO -- : <AutomationEngine> <AEMethod list_ec2_flavor_ids> $evm.object['values']: { 777000000000103=>"t2.nano on AWS Gov", 777000000000104=>"t2.micro on AWS Gov", 777000000000105=>"t2.small on AWS Gov", 777000000000106=>"t2.medium on AWS Gov", 777000000000107=>"t2.large on AWS Gov", 77000000000108=>"m3.medium on AWS Gov", 777000000000109=>"m3.large on AWS Gov", 777000000000110=>"m3.xlarge on AWS Gov", 777000000000111=>"m3.2xlarge on AWS Gov", 777000000000112=>"m4.large on AWS Gov", 777000000000113=>"m4.xlarge on AWS Gov", 777000000000114=>"m4.2xlarge on AWS Gov", 777000000000115=>"m4.4xlarge on AWS Gov", 777000000000116=>"m4.10xlarge on AWS Gov", 777000000000117=>"c3.large on AWS Gov", 777000000000118=>"c3.xlarge on AWS Gov", 777000000000119=>"c3.2xlarge on AWS Gov", 777000000000120=>"c3.4xlarge on AWS Gov", 777000000000121=>"c3.8xlarge on AWS Gov", 777000000000122=>"c4.large on AWS Gov", 777000000000123=>"c4.xlarge on AWS Gov", 777000000000124=>"c4.2xlarge on AWS Gov", 777000000000125=>"c4.4xlarge on AWS Gov", 777000000000126=>"c4.8xlarge on AWS Gov", 777000000000127=>"g2.2xlarge on AWS Gov", 777000000000128=>"g2.8xlarge on AWS Gov", 777000000000129=>"r3.large on AWS Gov", 777000000000130=>"r3.xlarge on AWS Gov", 777000000000131=>"r3.2xlarge on AWS Gov", 777000000000132=>"r3.4xlarge on AWS Gov", 777000000000133=>"r3.8xlarge on AWS Gov", 777000000000134=>"i2.xlarge on AWS Gov", 777000000000135=>"i2.2xlarge on AWS Gov", 777000000000136=>"i2.4xlarge on AWS Gov", 777000000000137=>"i2.8xlarge on AWS Gov", 777000000000138=>"d2.xlarge on AWS Gov", 777000000000139=>"d2.2xlarge on AWS Gov", 777000000000140=>"d2.4xlarge on AWS Gov", 777000000000141=>"d2.8xlarge on AWS Gov", 777000000000142=>"t1.micro on AWS Gov", 777000000000143=>"m1.small on AWS Gov", 777000000000144=>"m1.medium on AWS Gov", 777000000000145=>"m1.large on AWS Gov", 777000000000146=>"m1.xlarge on AWS Gov", 777000000000147=>"c1.medium on AWS Gov", 777000000000148=>"c1.xlarge on AWS Gov", 777000000000149=>"cc2.8xlarge on AWS Gov", 777000000000150=>"cg1.4xlarge on AWS Gov", 777000000000151=>"m2.xlarge on AWS Gov", 777000000000152=>"m2.2xlarge on AWS Gov", 777000000000153=>"m2.4xlarge on AWS Gov", 777000000000154=>"cr1.8xlarge on AWS Gov", 777000000000155=>"hi1.4xlarge on AWS Gov", 777000000000156=>"hs1.8xlarge on AWS Gov", 777000000000157=>"cc1.4xlarge on AWS Gov" } ===== Customer indicates that many of these 'flavors' are not actually available in AWS GovCloud (eg,m4.large) and should not be presented in dropdown list Expected results: only 'flavors' supported by AWS GovCloud should be instantiated into provisioning dynamic dropdown list Additional info: Customer indicates that his users are selecting 'flavors' that are not supported and are calling him to report this as a bug.
Marcel, Since this BZ was opened, we have become aware that since this is a AWS GovCloud environment, there are some process changes that RH needs to engage for problem reporting and working. When this gets properly arranged, I will ask the customer for their custom code for 'list_ec2_flavor_ids' but I will not be the least bit surprised if we find that this environment, since it is derived from the commercial AWS, is simply returning an unaltered list of 'flavors' just as it would from that environment, but that the AWS GovCloud is not configured to actually support the same range as the commercial environment. Tom Hennessy
Tom, I won't be surprised if you're right, re: comment #3. The problem here is that we can only present the flavors that the provider tells us about. If they show us flavors that are actually unavailable in that environment, then I think the customer needs to open a case with Amazon to get that resolved. But, like you said, we'll get the process figured out first. :)
PR https://github.com/ManageIQ/manageiq-providers-amazon/pull/38
https://github.com/ManageIQ/manageiq-providers-amazon/pull/44
New commit detected on ManageIQ/manageiq/master: https://github.com/ManageIQ/manageiq/commit/05299c2a9e4686a995c408a2c51534fe93495311 commit 05299c2a9e4686a995c408a2c51534fe93495311 Author: Marcel Hild <hild> AuthorDate: Thu Oct 13 14:55:46 2016 +0200 Commit: Marcel Hild <hild> CommitDate: Thu Oct 13 14:55:46 2016 +0200 config setting for amazon provider to disable regions at runtime https://bugzilla.redhat.com/show_bug.cgi?id=1346065 config/settings.yml | 2 ++ 1 file changed, 2 insertions(+)
New commit detected on ManageIQ/manageiq/euwe: https://github.com/ManageIQ/manageiq/commit/8234ba837d0d503830109fb75980da10a3d3fddb commit 8234ba837d0d503830109fb75980da10a3d3fddb Author: Greg Blomquist <blomquisg> AuthorDate: Mon Oct 17 09:40:17 2016 -0400 Commit: Oleg Barenboim <chessbyte> CommitDate: Tue Oct 18 17:23:23 2016 -0500 Merge pull request #11912 from durandom/disable_regions config setting for amazon provider to disable regions at runtime (cherry picked from commit e16cd14e4c696934cbe36d3bb371799366f7002f) https://bugzilla.redhat.com/show_bug.cgi?id=1346065 config/settings.yml | 2 ++ 1 file changed, 2 insertions(+)
https://github.com/ManageIQ/manageiq/pull/12119
https://github.com/ManageIQ/manageiq-providers-amazon/pull/44 https://github.com/ManageIQ/manageiq/pull/11912
For QE and doc team: It is now possible to disable amazon regions by modifying advanced configuration settings. Navigate to Config -> Settings -> Advanced and find :ems_amazon: :disabled_regions: [] Change it to e.g. :ems_amazon: :disabled_regions: - us-gov-west-1 - ap-northeast-1 to disable these two regions.
This is working just like the Azure Gov tests I already performed. Users can disable any region they want as long as they retrieve the internal name as described in comment 16. Moving to verified.