We have started seeing an issue in two seperate environments where something on our source Content Library is removing the files from our Content Library datastore. In both environments we have one CL master and 4 other vCenters subscribed to it. In the master CL it shows 43 items, but if we look on the datastore, there are only 15 folders and of those only 9 still have files in them. If we attempt to deploy a VM template from the master CL that does not exist, it errors out as you would expect. On all of the subscribed vCenters we are having no issues, all 43 of the items listed in the CL do exist on disk, so this only affects the CL master, none of the CL's that subscribe to it (thankfully) are missing files. I cant imagine this is any kind of intended behavior, to leave the CL listing, but delete the actual files? We are seeing the same thing on a completely separate/isolated vCenter that has 3 subscribers.
Current version: vCenter v6.7.0 Build 17137327
The master Content Library is on an NFS v3 datastore, but so are all of the subscribed ones. We have opened a case with VMware Fed Support, but nothing has come up yet.
So if you are using this version of vCenter, you might want to verify that your CL item count on your master CL matches the directory count on the CL datastore. I would love to know if anyone else is seeing this behavior. It *appears* to be deleting files by age, since our newest files are the ones that hang around the longest, but I cant swear to this.