Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-3873

Failed to create AWS Spot Instances with AWS AMI "RHEL-7.9_HVM-20221027-x86_64-0-Access2-GP2"

    • None
    • None
    • rhel-sst-program
    • None
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • If docs needed, set a value
    • 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?

              pm-rhel pm-rhel
              rhn-support-jaykim Jihoon Kim
              RH Bugzilla Integration RH Bugzilla Integration
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

                Created:
                Updated:
                Resolved: