← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1988803] Re: With image-volume cache enabled backend, volume creation for a smaller volume than image-volume cache has the same size of image-volume cache

 

** Also affects: nova
   Importance: Undecided
       Status: New

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

Title:
  With image-volume cache enabled backend, volume creation for a smaller
  volume than image-volume cache has the same size of image-volume cache

Status in Cinder:
  New
Status in OpenStack Compute (nova):
  New

Bug description:
  The issue is initially reported at
  https://bugzilla.redhat.com/show_bug.cgi?id=2100697.

  In the current implementation, cinder doesn't have a check point of the volume size when image volume cache is enabled.
  Due to that, the created volume whose requested size is smaller than the image cache volume has the same size of the image cache volume.
   
  Reproducing steps:
  1. Enable volume image cache feature in cinder.
  2. Upload a cirros image to glance
  3. Create a volume, Volume A,(e.g. 5GB) with the image as the first volume with the image.
  4. Then create a smaller volume, Volume B, (e.g. 1GB) with the image.
  5. Check actual volume image size on storage backend side.

  Current behavior:
  Volume A and Volume B have the same size(e.g. 5GB)
  However, cinder shows Volume A is 5GB and Volume B is 1GB.

  Expected behavior:
  Volume A and Volume B have different size based on their requested size(Volume A is 5GB, Volume B is 1GB).

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