yahoo-eng-team team mailing list archive

[Julie Pichon <1337278@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

The RAM checks always pass because we're comparing GB against MB - the
image minimum RAM is returned in GB while the flavour minimum RAM is
returned in MB.

Steps to reproduce:
1. Create a new image and set its minimum requirement to 8GB disk, 8GB RAM.
2. Try to launch an instance and select the new image

Actual result:
3. Minimum flavour is set to m1.small even though 

Expected result:
3. Flavour should be at least m1.large (using the devstack default flavours) since it offers 80GB disk/8,192 MB, m1.small should be disabled.


If you add some debug statements around the related code, you'll see we're comparing 8 against 512 / 2048 / etc.
https://github.com/openstack/horizon/blob/759e497b0d/horizon/static/horizon/js/horizon.quota.js#L99

** Affects: horizon
     Importance: Medium
         Status: New

-- 
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/1337278

Title:
  Client-side checks for flavor requirements not working correctly for
  RAM

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  The RAM checks always pass because we're comparing GB against MB - the
  image minimum RAM is returned in GB while the flavour minimum RAM is
  returned in MB.

  Steps to reproduce:
  1. Create a new image and set its minimum requirement to 8GB disk, 8GB RAM.
  2. Try to launch an instance and select the new image

  Actual result:
  3. Minimum flavour is set to m1.small even though 

  Expected result:
  3. Flavour should be at least m1.large (using the devstack default flavours) since it offers 80GB disk/8,192 MB, m1.small should be disabled.

  
  If you add some debug statements around the related code, you'll see we're comparing 8 against 512 / 2048 / etc.
  https://github.com/openstack/horizon/blob/759e497b0d/horizon/static/horizon/js/horizon.quota.js#L99

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