Bug 1380782

Summary: [RFE]VMware thick disk format provisioning
Product: Red Hat CloudForms Management Engine Reporter: Leo Khomenko <lkhomenk>
Component: ProvidersAssignee: John Hardy <jhardy>
Status: CLOSED WORKSFORME QA Contact: Dave Johnson <dajohnso>
Severity: medium Docs Contact:
Priority: medium    
Version: 5.6.0CC: dajohnso, jfrey, jhardy, kkulkarn, lcouzens, obarenbo
Target Milestone: GAKeywords: FutureFeature
Target Release: cfme-future   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: vsphere:vm:provision
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-03-11 18:41:34 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: CFME Core Target Upstream Version:
Attachments:
Description Flags
CFME screen
none
vCenter screen
none
request screen none

Description Leo Khomenko 2016-09-30 14:27:42 UTC
Created attachment 1206302 [details]
CFME screen

Description of problem:impossible to provision VM with thick disk.


Version-Release number of selected component (if applicable):


How reproducible:100%


Steps to Reproduce:
1.add vsphere provider
2.create Vm provision request with Thick Disk Format selected(on hardware tab)
3.Check Vm after request is completed

Actual results: Thin Provisioning used = True


Expected results: False


Additional info:

Comment 2 Leo Khomenko 2016-09-30 14:28:50 UTC
Created attachment 1206303 [details]
vCenter screen

Comment 3 Leo Khomenko 2016-09-30 14:29:16 UTC
Created attachment 1206304 [details]
request screen

Comment 5 Adam Grare 2016-10-10 19:45:21 UTC
I tested a number of scenarios and wasn't able to reproduce this.

I created two templates, one with a thick prov disk and one with a thin prov disk.  I then provisioned VMs from these through MIQ and switched the provision type on the hardware tab and confirmed it honored the disk format set in the provision dialog.  I did this for both vSphere 5.5 and vSphere 6.0 and all VMs ended up being provisioned correctly.

Can you set the log level and level_vim to debug and reproduce?  Also can you try the same thing but using just the vSphere web client to make sure it isn't just that the datastore doesn't support thick provisioned disks (e.g.: NFS)

Comment 6 Leo Khomenko 2016-10-19 15:14:30 UTC
yes, Adam is totally right. if data-storage is not available for thick disk provisioning it would be great to have additional notification/check/warning on if selected selected Disk type fits Data-storage

Can/should we do this?

Comment 7 Adam Grare 2016-10-19 15:26:07 UTC
Thanks Leo, when you provision a VM from a template you can set the virtual disk format just like in MIQ.  If the target datastore is an NFS share the only option is Thin Provisioned, it would be great to do the same thing in the MIQ provision dialog.

If we can find where this capability is stored and add it to inventory then we can filter the options for that dropdown.

Comment 9 Lucy Fu 2017-04-12 19:12:44 UTC
*** Bug 1430361 has been marked as a duplicate of this bug. ***

Comment 11 Kedar Kulkarni 2019-03-11 18:41:34 UTC
I chose a template that was thin provisioned and provisioned a VM with it, while setting disk to be "Thick" provisioned. It worked fine. I am closing this BZ.
Tested on 5.10.1.2.20190219165527_7a4a22b