Problem Statement

The customer reports that they are unable to select the correct AWS instance flavors in Satellite. Several AWS instance types are missing from the Flavor field, causing compute profiles configured with instances such as x2iedn.2xlarge to default unexpectedly to a1.medium.

User Experience & WorkflowRequirements

Workaround Applied

The customer followed the recommended workaround to rebuild the AWS flavors.rb file:

1.Backed up instances.json.

2.  Replaced incorrect architecture entries (arm64 and x86_64_mac ->  x86_64).

3.Regenerated and manually copied updated_flavors.rb into the Fog AWS gem directory (a missing step was identified and added).

4.Restarted Foreman.

5.Updated the compute profile flavor.

6.Successfully provisioned a new host.

This resolved the immediate issue.

The goal is to prevent this issue from happening again. Compute profiles use preselected AWS flavors, but when a flavor is missing from flavors.rb, Satellite automatically switches it to another (random) flavor. This change isn’t noticeable until a new host build is attempted, and in this case, the flavor was even switched to a different architecture.

Business Impact

[What would happen if the inclusion of this feature wasn’t undertaken?
Would any projects at Red Hat be negatively affected?]