Description of problem: https://aws.amazon.com/blogs/aws/new-amd-epyc-powered-amazon-ec2-m5ad-and-r5ad-instances/ https://aws.amazon.com/about-aws/whats-new/2019/02/introducing-five-new-amazon-ec2-bare-metal-instances/ Version-Release number of selected component (if applicable): 5.10.4.1 How reproducible: Always Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
PR: https://github.com/ManageIQ/manageiq-providers-amazon/pull/532
PR merged
Verification failed. r5d.metal and z1d.metal are still not in CFME. I created new BZ where these two instance types are included: https://bugzilla.redhat.com/show_bug.cgi?id=1724686 Maybe this BZ can be verified/closed in favor of the other BZ.
Matous, looks like the missing types are covered in a separate BZ, so I think it makes sense to move this to VERIFIED. If you do, please update the BZ summary to remove types not yet included :)
Okay then verified in 5.11.0.10. Instance types are now in CFME.
Matous, r5, r5d, and z1d "bare" instances have no "metal" word in their names. It is defined by the AWS price-list API. They named just "r5" and so on. I understand there is no naming consistency with other "metal" instance types, like "m5.metal", but this is what we have on the AWS side and in thir gem/API. If we'll start to name it on our own, we should expect issues when provisioning them.
Created attachment 1593435 [details] metal instances Alex, I am checking the list from CFME Flavors with instance types that are available for launch from AWS Console. r5/r5d/z1d instances have "metal" world in their name. I would say it makes sense to have it the same way as AWS console has.
Fixed in https://bugzilla.redhat.com/show_bug.cgi?id=1724686