Bug 1072204

Summary:	[Doc] When Launching a new Instance, all flavors are displayed regardless of the image requirements
Product:	Red Hat OpenStack	Reporter:	Summer Long <slong>
Component:	doc-Getting_Started_Guide	Assignee:	Deepti Navale <dnavale>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Bruce Reeler <breeler>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	2.1	CC:	breeler, rlandman, yeylon
Target Milestone:	---	Keywords:	Documentation, Triaged
Target Release:	5.0 (RHEL 7)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	906302	Environment:
Last Closed:	2014-09-04 13:07:21 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	906302
Bug Blocks:

Description Summer Long 2014-03-04 06:22:22 UTC

+++ This bug was initially created as a clone of Bug #906302 +++
Description of problem:
Reported by aortega. Regardless of an image's disk and RAM requirements, all flavors are available in the drop-down menu when Launching an instance. Therefore you can end up using e.g. a m1.tiny flavour with 512Mb RAM with an image that requires at least 2Gb of RAM.

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

How reproducible:
Always

Steps to Reproduce:
1. Create a new image, setting the minimum RAM requirement to 2048MB
2. After the image is uploaded, try to Launch it
  
Actual results:
The flavor selected by default is m1.tiny, which doesn't actually provide enough RAM for the image.
After clicking Launch, the instance fails to launch with an error "Instance type's memory is too small for requested image. (HTTP 400)"

Expected results:
Horizon should default to an appropriate flavor, and probably prevent the user from launching an image with a flavor that doesn't meet the image's requirements.
The UI should also be enhanced to display the image's requirements. At the moment, there is no indication what an image's requirements are when launching a new instance.

Comment 2 Bruce Reeler 2014-03-06 07:51:56 UTC

This bug is being assigned to dnavale, who is now the designated docs specialist
for horizon.
Setting Priority and Severity same as parent bug for now.

Deepti:
I could not see where the GSG specifically shows the flavors when one is using horizon, it does not seem to list them, only saying "Select a Flavor for your instance. The flavor determines the compute resources available to your instance. After a flavor is selected, their resources are displayed in the Flavor Details pane for preview."
Fig 7.5 lists 'tiny', but it is only an example screenshot.

If these flavors are now correctly limited in the dashboard's dropdown, depending on image selected, I'm not sure it actually requires a fix in the GSG's dashboard description?

Comment 4 Bruce Reeler 2014-05-23 05:08:14 UTC

Checked, its there.

Comment 6 Deepti Navale 2014-06-17 04:15:25 UTC

Bruce, 

Since you have already checked for this, could you change to VERIFIED. 

Thanks.