-
Bug
-
Resolution: Cannot Reproduce
-
Undefined
-
rhel-7.9.z
-
None
-
None
-
rhel-sst-program
-
None
-
False
-
-
None
-
None
-
None
-
None
-
If docs needed, set a value
-
-
Unspecified
-
None
Description of problem:
Failed to set "specify instance attributes" in ASG configuration when using RHEL-7.9_HVM-20221027-x86_64-0-Access2-GP2 AMI which is owned by Red Hat.
How reproducible:
Since this is Auto Scaling Group configuration from AWS, I was not able to run a test. But according to the customer:
Steps to Reproduce:
1. Create "Launch Template" and ASG
2. During ASG configuration, when the Customer uses "Specify instance attributes" with "no minimum" and "no maximum" to vcpu and memory it returns the error "Launching a new EC2 instance. Status Reason: Internal error. Launching EC2 instance failed."
3. It happens only when the customer uses AMIs owned by Redhat. When they use Red Hat AMI owned by AWS, it works.
Actual results:
- "Launching a new EC2 instance. Status Reason: Internal error. Launching EC2 instance failed."
Expected results:
- able to create ASG
Additional info:
- When the customer uses AMI "RHEL-7.9_HVM-20221027-x86_64-0-Hourly2-GP2" spot instances with "specify instance attributes", it works, but if the Customer uses AMI "RHEL-7.9_HVM-20221027-x86_64-0-Access2-GP2" it failed,
What's the difference between these two AMIs?
- external trackers