Project

General

Profile

Bug #7118

EC2: Changing image doesn't update available flavors list.

Added by Ashton Davis about 6 years ago. Updated over 2 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Compute resources - EC2
Target version:
-
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:

Description

This is a bug with images in EC2

Issue: Available flavors list (t1, m3, r3, etc) seems to be pulled for the first image attached to the compute resource, and the list doesn't update when the image is changed.

For instance - the first image I attached to the resource was a Paravirtualized Instance Store-backed linux image. This image can't provision on r-class flavors, which require HVM. So I attached an HVM image - but the flavors list doesn't change, I still can't provision r-class flavors.

Steps to replicate:
1) Create EC2 compute resource
2) Add PV EBS or Instance AMI to the compute resource
3) Observe available flavors
4) Add VM AMI to the resource
5) Observe available flavors again - see that r is still not present, no matter how you try to load the form.

History

#1 Updated by Ville Liski about 6 years ago

This issue is also reproducible by:
1) Add new EC2 Compute Resource
2) Add one new paravirtualized image to previously created Compute Resource
3) Add new EC2 Compute Resource with same Access Key
4) Add one new hvm image to newest Compute Resource
5) Observe available flavors again - see that r is still not present, no matter how you try to load the form.

#2 Updated by TJ Wright about 5 years ago

The flavors are hard coded in fog.
https://github.com/fog/fog-aws/commits/master/lib/fog/aws/models/compute/flavors.rb

I haven't tried it yet, but am assuming you can update the flavors.rb and restart foreman.

#3 Updated by TJ Wright about 5 years ago

FYI, no foreman restart is necessary. Just update the flavors.rb file and get the form to re-render.

Also available in: Atom PDF