Bug 1562062 - Newest EC2 t2 instance types are missing in CFME
Summary: Newest EC2 t2 instance types are missing in CFME
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Providers
Version: 5.9.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: GA
: 5.10.0
Assignee: Alexander Zagaynov
QA Contact: Matouš Mojžíš
URL:
Whiteboard: ec2
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-03-29 12:59 UTC by Matouš Mojžíš
Modified: 2019-02-07 23:01 UTC (History)
7 users (show)

Fixed In Version: 5.10.0.11
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-02-07 23:01:30 UTC
Category: ---
Cloudforms Team: AWS
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2019:0212 0 None None None 2019-02-07 23:01:37 UTC

Description Matouš Mojžíš 2018-03-29 12:59:08 UTC 
Description of problem:
Announced here: https://aws.amazon.com/about-aws/whats-new/2018/03/amazon-ec2-t2-instance-types-are-now-supported-on-windows-with-sql-server-enterprise/
t2.xlarge and t2.2xlarge instance types are missing in CFME

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

How reproducible:
Always

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 2 Alexander Zagaynov 2018-05-04 13:36:08 UTC 
Related issues:
https://github.com/ManageIQ/manageiq-providers-amazon/issues/396
https://github.com/ManageIQ/manageiq-providers-amazon/issues/397
Comment 3 Alexander Zagaynov 2018-07-03 13:40:39 UTC 
PR: https://github.com/ManageIQ/manageiq-providers-amazon/pull/449
Comment 4 Alexander Zagaynov 2018-08-15 10:40:24 UTC 
PR merged.
Comment 5 Matouš Mojžíš 2018-08-17 17:19:06 UTC 
Verified in 5.10.0.11. Newest t2 instance types are listed in flavor list.
Comment 7 errata-xmlrpc 2019-02-07 23:01:30 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://access.redhat.com/errata/RHSA-2019:0212
Note You need to log in before you can comment on or make changes to this bug.