← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1602740] [NEW] VMware: Sparse disks get attached to the instance as lazy zeroed thick disks instead of thin provisioned disks

 

Public bug reported:

Description
===========
As per the documentation "Sparse disks get imported from the OpenStack Image service into ESX as thin provisioned disks"

http://docs.openstack.org/kilo/config-reference/content/vmware.html

But its being set as lazy zeroedthick disk.

Steps to reproduce
==================
1) Upload a sparse disk and set the the vmware_disktype="sparse".
2) Create an instance
3) Edit the VM from vsphere client, disk provisioning type will be displayed as 
"Thick provision lazy zeroed"


Expected result
===============
Disk provisioning can be Thin provision/ sparse provision.

Actual result
=============
disk provisioning type is set as "Thick provision lazy zeroed"

Environment
===========
1. Devstack stable/mitaka

2. Which hypervisor did you use?
   VMWare

3. What's the version of that?
   5.5


Logs & Configs
==============
attaching the snapshot

** Affects: nova
     Importance: Undecided
         Status: New


** Tags: vmware

** Attachment added: "instances settings"
   https://bugs.launchpad.net/bugs/1602740/+attachment/4700242/+files/Capture.PNG

** Summary changed:

- Sparse disks get attached to the instance as lazy zeroed thick disks instead of thin provisioned disks
+ VMware: Sparse disks get attached to the instance as lazy zeroed thick disks instead of thin provisioned disks

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

Title:
  VMware: Sparse disks get attached to the instance as lazy zeroed thick
  disks instead of thin provisioned disks

Status in OpenStack Compute (nova):
  New

Bug description:
  Description
  ===========
  As per the documentation "Sparse disks get imported from the OpenStack Image service into ESX as thin provisioned disks"

  http://docs.openstack.org/kilo/config-reference/content/vmware.html

  But its being set as lazy zeroedthick disk.

  Steps to reproduce
  ==================
  1) Upload a sparse disk and set the the vmware_disktype="sparse".
  2) Create an instance
  3) Edit the VM from vsphere client, disk provisioning type will be displayed as 
  "Thick provision lazy zeroed"

  
  Expected result
  ===============
  Disk provisioning can be Thin provision/ sparse provision.

  Actual result
  =============
  disk provisioning type is set as "Thick provision lazy zeroed"

  Environment
  ===========
  1. Devstack stable/mitaka

  2. Which hypervisor did you use?
     VMWare

  3. What's the version of that?
     5.5

  
  Logs & Configs
  ==============
  attaching the snapshot

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


Follow ups