Problem: Hosts deployed from Image based provisioning on VMWare are deployed as thick provisioned even though “Thin Provision” is selected.
I am currently trying to create new hosts based on a VMWare template, everything works ok so far (thanks to reading through a lot of topics in this community). The only issue I am having is that the host is created with a “Thick Provisioned Lazy Zeroed” disk, meanwhile I am selecting “Thin Provision” on the Virtual Machine tab under storage configuration.
Expected outcome:
New VM should be deployed with a thin provisioned disk.
Foreman and Proxy versions: 1.16.1
Foreman and Proxy plugin versions:
foreman_setup 5.0.0
Other relevant data:
Currently using VMWare vCenter, with a vSAN cluster. Hypervisors version: VMware ESXi, 6.5.0, 7388607
Please let me know what log files should I paste that might help.
Can I get a foreman-debug from your foreman-instance so I can look further. We do have an open BZ on that downstream but I swear that was fixed not too long ago. Maybe it was and there is regression now, either way email me a foreman-debug at chrobert@redhat.com
I am using VSAN. I checked the storage policy and it is set to thin-provision. When I try to deploy the VM from the same template on vCenter the machine i get is thin-provisioned as expected.
Just for some additional clarification. I used the same foreman instance to provision on an other ESXI host which has a local datastore and got the same results.
Ok good to know it is not isolated to VSAN, I will try with localstorage. I am just getting an image spun up and created. I do not have a VSAN license so thank you for letting me know that.
I remember trying the PXE Mode installation and the image was deployed as Thin-Provision. I didnt try setting it as thick provisioned though.
Im not sure if Bug:1378579 is directly related to our issue, since it looks like it has the opposite outcome where the image is deployed as thin provisioned.
However I would really appreciate if you can pick up this bug.
Thank you very much @cintrix84, I really appreciate it!
Another data point here, I can confirm this problem also exists in 1.18. I am unable to deploy a VM template using image as thin when the template is thick.
Sorry for the long delay, I am finishing up 1 high priority bug for our downstream release and then will start to look at this more. I already have it assigned to me to look at.
Looks like I am impacted by this as well. Technically I’m running Satellite, but it worked correctly before a recent upgrade. I am going back through my recently provisioned hosts to try and figure out exactly when it stopped working correctly.
The VM attributes are very picky about data entry. The exact before and after are below… and in my opinion… what I had before should have worked and it didn’t. Synopsis below,
I upgraded to 1.20.1 today and nothing changed for me, a new VM from a thin provision image was created with lazy zeroed storage.
Can you explain your old workaround?
Thanks