Description of problem: https://aws.amazon.com/about-aws/whats-new/2018/09/amazon-ec2-f1-instances-now-available-in-an-additional-size/ Version-Release number of selected component (if applicable): 5.10.0.18 How reproducible: Always Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
It was fixed with https://github.com/ManageIQ/manageiq-providers-amazon/pull/493
New commit detected on ManageIQ/manageiq-providers-amazon/hammer: https://github.com/ManageIQ/manageiq-providers-amazon/commit/e229f18ee1e31119df0e176e9ac7daa20c977cc0 commit e229f18ee1e31119df0e176e9ac7daa20c977cc0 Author: Bronagh Sorota <bsorota> AuthorDate: Thu Oct 4 13:03:02 2018 -0400 Commit: Bronagh Sorota <bsorota> CommitDate: Thu Oct 4 13:03:02 2018 -0400 Merge pull request #493 from AlexanderZagaynov/updates/ec2_f1_new_size new AWS EC2 instance types (cherry picked from commit a9f1252e2066231233273693c86595b189f87892) https://bugzilla.redhat.com/show_bug.cgi?id=1623094 https://bugzilla.redhat.com/show_bug.cgi?id=1636182 db/fixtures/aws_instance_types.yml | 232 + spec/models/manageiq/providers/amazon/aws_refresher_spec_counts.rb | 2 +- spec/models/manageiq/providers/amazon/cloud_manager/stubbed_refresher_spec.rb | 2 +- 3 files changed, 234 insertions(+), 2 deletions(-)
Verified in 5.10.0.23. F1.4xlarge flavor is in CFME.
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