Launching an instance from image, insufficient flavors not filtered

[Tzach Shefi]

Description of problem: While selecting an image from Glance images, you can click on "Lunch" button to boot an instance. This opens up an instance boot page, on this page flavors with insufficient disk size are not automatically "grayed out". However if you reach this same location from instance page and chose an image, assuming image has min disk option, insufficient flavors are grayed out automatically.

Might be a case for another bug, on instance boot page, image selection should be given a higher priority in the flow, thus flavor list would be updated automatically. Rather then selecting a flavor then choosing an image only to find that disk is too small for selected image.

Version-Release number of selected component (if applicable):
rhel 6.5
python-django-horizon-2014.1.1-2.el6ost.noarch

How reproducible:
Every time

Steps to Reproduce:
1. Upload an image, make sure to set min disk setting
2. On images page, click "lunch" button of image created above
3. Notice insufficient flavors are not grayed out.
4. While if you start procedure not from images but rather instances, it does happen.

Actual results:
All instance flavors are available.

Expected results:
It would be nice if insufficient flavors would be grayed out automatically. As they are when using instance page to launch an instance, selecting an image causes small flavors to become disabled.

[Julie Pichon (jpichon)]

I can't reproduce on master with devstack:

1. Create a new image with min disk 2GB
2. Click on Launch once the image is ready: "m1.small" is the first selected flavour as expected.

[Julie Pichon (jpichon)]

(and the other smaller options are greyed out)

[Cindy Lu (clu-m)]

I followed Julie's steps. 'Launch as Instance' from Image and 'Launch Instance' seem to work the same way in disabling/greying out the flavors that don't match image requirements.

I will mark this as Invalid unless it comes up again. :)