You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cloudstack.apache.org by GitBox <gi...@apache.org> on 2018/09/11 18:55:33 UTC

[GitHub] resmo commented on issue #2840: Fix for Vmware full clones update

resmo commented on issue #2840: Fix for Vmware full clones update
URL: https://github.com/apache/cloudstack/pull/2840#issuecomment-420383017
 
 
   I wonder why does cloudstack make any assumption based on a database record and not of the vmware vsphere API if the volume is a linked or full clone. 
   
   Let's assume we have a `vmware.create.full.clone = false` and create a VM. After that we storage migrate the VM. The linked clone becomes a full clone, however, cloudstack still handles it as linked clone because the database says so. 
   
   Does this make any sense?

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services