Bug 1072205 - [Doc] When Launching a new Instance, all flavors are displayed regardless of the image requirements
Summary: [Doc] When Launching a new Instance, all flavors are displayed regardless of ...
Keywords:
Status: CLOSED DUPLICATE of bug 1084274
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: doc-User_Guide
Version: 2.1
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 5.0 (RHEL 7)
Assignee: Deepti Navale
QA Contact: ecs-bugs
URL:
Whiteboard:
Depends On: 906302
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-03-04 06:22 UTC by Summer Long
Modified: 2014-04-23 00:30 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 906302
Environment:
Last Closed: 2014-04-23 00:30:54 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Summer Long 2014-03-04 06:22:25 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 Martin Lopes 2014-03-16 23:34:51 UTC
This bug is being assigned to Deepti Navale, who is now the designated docs specialist for Dashboard.

Comment 3 Deepti Navale 2014-04-23 00:30:54 UTC

*** This bug has been marked as a duplicate of bug 1084274 ***


Note You need to log in before you can comment on or make changes to this bug.