yahoo-eng-team team mailing list archive

[Ying Zuo <yinzuo@xxxxxxxxx>]

Public bug reported:

Steps to reproduce:

1. Create a flavor with zero root disk

2. Create an image with minimum disk size as 10GB

3. Try to launch an instance from the image created in step 2 from
either the Angular launch instance modal or the Python launch instance
modal. You will get a help message indicating the flavor created in step
1 is not a valid option because it doesn't meet the minimum disk size
set in the image.


I noticed a few issues:

1. On the Python launch instance modal, the help text message is
overlapping with the next input label. Also, the user can't really tell
which flavors are disabled because all flavors in the dropdown are
clickable and have the same text styling. However, after they click on a
disabled flavor, the selected option in the dropdown doesn't change.

2. The user won't be able to launch an instance with the zero disk
flavor with either Angular or Python launch instance modal. According to
the openstack guide[1], zero is a special case which uses the image size
for the instance. Thus flavors with zero disk size should not be
disabled because of the image disk requirement.

[1] http://docs.openstack.org/admin-guide/compute-flavors.html

** Affects: horizon
     Importance: Undecided
     Assignee: Ying Zuo (yingzuo)
         Status: New

** Changed in: horizon
     Assignee: (unassigned) => Ying Zuo (yingzuo)

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

Title:
  Flavors with zero disk size should not be disabled

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  Steps to reproduce:

  1. Create a flavor with zero root disk

  2. Create an image with minimum disk size as 10GB

  3. Try to launch an instance from the image created in step 2 from
  either the Angular launch instance modal or the Python launch instance
  modal. You will get a help message indicating the flavor created in
  step 1 is not a valid option because it doesn't meet the minimum disk
  size set in the image.

  
  I noticed a few issues:

  1. On the Python launch instance modal, the help text message is
  overlapping with the next input label. Also, the user can't really
  tell which flavors are disabled because all flavors in the dropdown
  are clickable and have the same text styling. However, after they
  click on a disabled flavor, the selected option in the dropdown
  doesn't change.

  2. The user won't be able to launch an instance with the zero disk
  flavor with either Angular or Python launch instance modal. According
  to the openstack guide[1], zero is a special case which uses the image
  size for the instance. Thus flavors with zero disk size should not be
  disabled because of the image disk requirement.

  [1] http://docs.openstack.org/admin-guide/compute-flavors.html

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