In a VDC with fast-provisioning enabled, I deploy a consolidated template, which creates a minimal footprint linked clone. Then I use the vCD UI to add a disk to a deployed VM. In vCenter this creates a standalone disk file _with the linked clone_. Yet now vCD will not let me expand nor delete this disk, claiming it is because the VM is fast-provisioned. I do not see the rationale, since nothing is linked to this disk. Is it just being conservative because theoretically a further clone COULD be linked back to it? But then you should observe the same behavior for a consolidated VM in the same VDC, which is not the case. It seems like vCD is unnecessarily restricting all disks in the entire VM from being modified, just because some other of its disks were fast-provisioned.
Is this what others observe? Does VMware have plans to remove this restriction?
Thanks for your response, but the issue is specifically about the fast provisioning. As mentioned on your third link, "One additional thing you should be aware of, is that you will not be able to resize or hot-extend a virtual disk for a Fast Provisioned VM in vCloud Director." That is exactly the issue I am asking about. I understand the limitation referred to if the disk itself is a fast-provisioned copy, but we are observing inability to expand or delete even a disk ADDED to a fast-provisioned VM that itself has no clones or snapshots. It does not matter whether API or GUI is used. Is this a glitch VMware intends to fix, or is there a technical reason?