yahoo-eng-team team mailing list archive

[Thierry Carrez <thierry.carrez+lp@xxxxxxxxx>]

** Changed in: horizon
       Status: Fix Committed => Fix Released

** Changed in: horizon
    Milestone: None => icehouse-1

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1116122

Title:
  When Launching a new Instance, all flavors are displayed regardless of
  the image requirements

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  Regardless of an image's disk and RAM requirements, all flavors are
  available in the drop-down menu when Launching a new 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.

  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:
  3. 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
  message "Error: There was an error submitting the form. Please try
  again." (* )

  Expected results:
  3. 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.

  
  (*) This was on a recent grizzly devstack. I also tested in a Folsom devstack and received a better error message back: "Instance type's memory is too small for requested image. (HTTP 400)". This is still visible in the logs - RESP BODY: {"badRequest": {"message": "Instance type's memory is too small for requested image.", "code": 400}}. It's unfortunate we appear to have lost the clearer error message along the way.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1116122/+subscriptions