yahoo-eng-team team mailing list archive

[Adam Gandelman <1368600@xxxxxxxxxxxxxxxxxx>]

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

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

Title:
  Creating a volume from an instance snapshot should validate the volume
  size / min_disk

Status in OpenStack Dashboard (Horizon):
  Fix Committed
Status in OpenStack Dashboard (Horizon) icehouse series:
  Fix Released

Bug description:
  This is sort of a follow-up to bug 1241253. When an image is created
  based on an instance snapshot, even though the same min_disk
  restrictions apply, they're not reflected properly in the validation
  and tool tips, resulting in misleading information being shown to the
  user.

  Steps to reproduce:
  -------------------------
  1. Create an image with a minimum disk size of e.g. 2GB
  2. Boot an instance from the image
  3. Create a snapshot of the instance (from dashboard or using nova create-image)
  4. Back on the images panels, click the "Create volume" button for the new image
  5. The prefilled size and size tooltip do not indicate the correct minimum disk size

  
  This seems to be happening because in that case the min_disk attribute is set as a property rather than a direct attribute, looking at Glance:

  $ glance image-show <id_of_image>
  +------------------+--------------------------------------+
  | Property         | Value                                |
  +------------------+--------------------------------------+
  ...
  | min_disk         | 2                                    |
  ...

  $ glance image-show <id_of_instance_snapshot>
  +---------------------------------+------------------------+
  | Property                        | Value                  |
  +---------------------------------+------------------------+
  ...
  | Property 'min_disk'             | 2                      |
  ...
  | min_disk                        | 0                      |
  ...

  I'm not sure why... Maybe someone from Glance could shed some light on
  this and whether that's the expected behaviour?

  In the meantime it shouldn't be too hard for Horizon to handle the
  case where min_disk is set as a property.

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