Hi Mike, this bug has been addressed in the master branch and should be in version 4.15
Cheers Darrin ________________________________ From: Corey, Mike <[email protected]> Sent: Friday, October 16, 2020 4:44 PM To: [email protected] <[email protected]> Subject: Clean-up stale clones Hi, Running through my lab testing I seem to be collecting different copies of clones in my vCenter. I’m talking about the initial clone created when the very first instance is created from a template. I’ve since imported templates, created instances, and destroyed both but the initial clone of the template VM remains (VM is named uuid) in my vCenter. Why doesn’t CloudStack purge that automatically if/when a template is destroyed? It makes vCenter cluttered and also takes up space on my VMware storage. Another thing is that these template VM clones cause an error in the logs that, in my opinion, is just noise and unnecessary. (Unable to find matched VM in CloudStack DB. name: fb0f60a8b22637b8bd6c67d03a10196d) Mike Mike Corey Technology Senior Consultant, IT CS CTW Operation & Virtualization Service US SAP AMERICA, INC. 3999 West Chester Pike, Newtown Square, 19073 United States T +1 610 661 0905, M +1 484 274 2658, E [email protected] [cid:[email protected]] [email protected] www.shapeblue.com 3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK @shapeblue
