yahoo-eng-team team mailing list archive

[luogangyi <luogangyi@xxxxxxxxxxxxxxx>]

Public bug reported:

If we choose "boot from image" and the image is a file, we will get an instance with a local disk. The size of the local disk equals the flavor.
If we choose "boot from image(create new volume)", we will get an instance with a volume. The size of the volume equals the size we inputed in Dashboard.

However, if  we choose "boot from image" and the image is a snapshot, we
will get an instance with a volume. And the size of the volume equals
the size of snapshot instead of the size of flavor.

I am not sure whether it is a bug or it is designed  intentionally. But
I believe making the size of volume being consistent with flavor is
better in that situation.

How to reproduce:
1. Using "boot from image(create new volume)" to create a new volume-backed instance.
2. Taking a snapshot of this  volume-backed instance. This operation will add a snapshot-based image in Glance.
3. Using "boot from image" and choosing the snapshot-based image which created before. We will get volume-backed Instance.
 And the size of the root device(a volume)  equals to the size of shapshot instead of the size of flavor.

** Affects: nova
     Importance: Undecided
         Status: New

** Patch added: "nova-bdm-flavor.patch"
   https://bugs.launchpad.net/bugs/1380493/+attachment/4233850/+files/nova-bdm-flavor.patch

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

Title:
  Root device size is not consistent with flavor

Status in OpenStack Compute (Nova):
  New

Bug description:
  If we choose "boot from image" and the image is a file, we will get an instance with a local disk. The size of the local disk equals the flavor.
  If we choose "boot from image(create new volume)", we will get an instance with a volume. The size of the volume equals the size we inputed in Dashboard.

  However, if  we choose "boot from image" and the image is a snapshot,
  we will get an instance with a volume. And the size of the volume
  equals the size of snapshot instead of the size of flavor.

  I am not sure whether it is a bug or it is designed  intentionally.
  But I believe making the size of volume being consistent with flavor
  is better in that situation.

  How to reproduce:
  1. Using "boot from image(create new volume)" to create a new volume-backed instance.
  2. Taking a snapshot of this  volume-backed instance. This operation will add a snapshot-based image in Glance.
  3. Using "boot from image" and choosing the snapshot-based image which created before. We will get volume-backed Instance.
   And the size of the root device(a volume)  equals to the size of shapshot instead of the size of flavor.

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