Bug 1430361

Summary: Reconfiguring a vm adding a thick provisioned disk shows as thin provisioned afterwards
Product: Red Hat CloudForms Management Engine Reporter: luke couzens <lcouzens>
Component: AutomateAssignee: Lucy Fu <lufu>
Status: CLOSED DUPLICATE QA Contact: luke couzens <lcouzens>
Severity: medium Docs Contact:
Priority: medium    
Version: 5.8.0CC: abellott, gmccullo, jhardy, mkanoor, obarenbo, tfitzger
Target Milestone: GA   
Target Release: cfme-future   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: reconfigure
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-04-12 19:12:44 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
thick disk was added. none

Description luke couzens 2017-03-08 13:01:23 UTC 
Description of problem:Reconfiguring a vm from vmware by adding a thick provisioned disk shows as thin provisioned afterwards


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


How reproducible:100%


Steps to Reproduce:
1.login to appliance
2.add vsphere provider
3.create vm
4.reconfigure vm adding thick provisioned disk
5.look at vmware disks after completion

Actual results:all added disks show as Thin


Expected results:Thick provisioned shown


Additional info:
This was ran against a powered off vm
Comment 2 Lucy Fu 2017-03-13 20:33:07 UTC 
Created attachment 1262596 [details]
thick disk was added.
Comment 3 Lucy Fu 2017-03-13 20:37:09 UTC 
I was able to add a thick disk without any issue. 

However according to VMware document:
 On NFS datastores that do not support Hardware Acceleration, only thin format is available.

So please make sure the datastore that the new disk is added to supports thick disk format.
Comment 4 luke couzens 2017-03-14 10:36:37 UTC 
Hi Lucy,

Just checked this and you are correct, it seems the datastore needs to have hardware acceleration support to add thick provision disks.

So with that in mind if the datastore does not support 'Hardware Acceleration' should we not see an error message in cfme rather than just forcing the disk type to be a thin provision? 

Thanks,
Luke
Comment 5 Lucy Fu 2017-03-14 16:01:19 UTC 
This seems the same issue as BZ #1380782.

Adam is working on collecting and storing the info about hardware acceleration support of a datastore into our DB. Then UI may display the thick/thin disk format according to what are supported by the datastore.
Comment 6 Lucy Fu 2017-04-12 19:12:44 UTC 

*** This bug has been marked as a duplicate of bug 1380782 ***