I'm a VMware customer (not service provider) running vCD 5.5.6. In one environment (not replicated in others), vApp Templates are losing the base disk when a linked clone consolidation operation occurs.
As an example I have a VM and I add it to the catalog as either a new or update an existing vApp Template. Now that I have my template, I clean up and delete the VM in my cloud. The chain length of the vApp Template changes from 2 to 1 but the storage used shows as 0 bytes and the flat VMDK goes missing from the datastore. Deploying from the vApp Template results in a "file not found", "cannot create snapshot", "unable to create" error.
Another example, I deployed from a working vApp Template and force a consolidate on the fast provisioned linked clone. Both the VM and the vApp Template have a chain length of 1 but only the VM is usable. The vApp Template has now lost access to a flat VMDK.
Has anyone run into this before?
