To add to what Darrin said - the fix will only work for NOT producing NEW garbage with new templates - i.e. old garbage - you need to clear manually.
THose VM names (as you said, UUID-like names) are references (if used, of course...) in the template_spool_ref table, field local_path or install_path (which are the same for me, in latest ACS release) So I would advise to get a VM name (UUID-like name of the VM) in vCenter and search for it inside the template_spool_ref table - if no match - this means ACS has done (partial....) GC and has removed the template from the template_spool_ref table - but failed to remove it from ACS - you can manually remove it - this should be 100% safe in theory. Due to link clones, which you might be using - I would advise registering a new template, deploy new VM, stop VM, then TRY to delete the template VMf from vSphere directly - to see if the linked-clone setup (user VM volumes are linked clones of that UUID-like named VM) - if it allows it to be deleted... i.e. you want to see if that fails - meaning vSphere is protecting itself (haven't tested this) - and if this fails, than you are 101% safe to remove all those UUID-like named template VMs from |ACS, assuming they are not references in the template_spool_ref table. Let us know how it goes Best, On Fri, 16 Oct 2020 at 16:47, Darrin Hüsselmann < [email protected]> wrote: > 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 > > > > -- Andrija Panić
