← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1646740] [NEW] creation image for volume-backend instance should use volume size in image property 'min_disk'

 

Public bug reported:

Description
===========
Currently, Nova is using disk size in flavor to set min_disk property in image when creating instance snapshot, even if it's a volume-backend instance. If disk size in flavor is bigger than volume size, there is a issue that Nova will raise "Volume is smaller than the minimum size specified in image metadata" when use this image to create a new instance.

Nova should set min_disk just using volume size if it's a volume-backend
instance.

Steps to reproduce
==================
1. Create volume-backend instance with 1G size volume but flavor has 2G disk size.
2. Creation of instance is successful and then create a snapshot for this instance.
3. The image is created successfully, and the property min_disk of image is 2G.
4. Create a new instance by using this image.

Expected result
===============
The new instance created successfully.

Actual result
=============
Nova returns 400 error: " Volume is smaller than the minimum size specified in image metadata. Volume size is 1073741824 bytes, minimum size is 2147483648 bytes."


Environment
===========
commit 5f465e83e2c2987c7b546e2e73fd926c6956aa4b
Merge: c10ff21 19a52c9
Author: Jenkins <jenkins@xxxxxxxxxxxxxxxxxxxx>
Date:   Mon Nov 14 21:26:07 2016 +0000

    Merge "Remove ceph install/config functions from l-m hook"

hypervisor: libvirt+KVM
storage: LVM

** Affects: nova
     Importance: Undecided
     Assignee: wanghao (wanghao749)
         Status: New

** Changed in: nova
     Assignee: (unassigned) => wanghao (wanghao749)

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

Title:
  creation image for volume-backend instance should use volume size in
  image property 'min_disk'

Status in OpenStack Compute (nova):
  New

Bug description:
  Description
  ===========
  Currently, Nova is using disk size in flavor to set min_disk property in image when creating instance snapshot, even if it's a volume-backend instance. If disk size in flavor is bigger than volume size, there is a issue that Nova will raise "Volume is smaller than the minimum size specified in image metadata" when use this image to create a new instance.

  Nova should set min_disk just using volume size if it's a volume-
  backend instance.

  Steps to reproduce
  ==================
  1. Create volume-backend instance with 1G size volume but flavor has 2G disk size.
  2. Creation of instance is successful and then create a snapshot for this instance.
  3. The image is created successfully, and the property min_disk of image is 2G.
  4. Create a new instance by using this image.

  Expected result
  ===============
  The new instance created successfully.

  Actual result
  =============
  Nova returns 400 error: " Volume is smaller than the minimum size specified in image metadata. Volume size is 1073741824 bytes, minimum size is 2147483648 bytes."

  
  Environment
  ===========
  commit 5f465e83e2c2987c7b546e2e73fd926c6956aa4b
  Merge: c10ff21 19a52c9
  Author: Jenkins <jenkins@xxxxxxxxxxxxxxxxxxxx>
  Date:   Mon Nov 14 21:26:07 2016 +0000

      Merge "Remove ceph install/config functions from l-m hook"

  hypervisor: libvirt+KVM
  storage: LVM

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