We recently migrated to View Horizon 5.3 from 5.2 on all new infrastructure and we're seeing a behavior with our floating pool that we didn't see before. We have a large floating pool based on Linked Clones and whenever vCenter/vComposer tears down and rebuilds a machine it isn't re-using the old machine's datastore folder, it's creating a new one _1, _2, _3, etc. The first machine in the pool has been rebuild 9 times since Friday and it's leaving behind a folder with ~200MB of data in the from of two .vmdk files.
We're not seeing any errors on the composer tasks during the rebuild, no datastore based errors (locked files, etc.). I've searched and come up with zip so far. Any obvious ideas before I open a case?
