metadata file copy results in error 'Content import of FILENAME failed - must be an existing file'
similar to https://pulp.plan.io/issues/1944
Its currently unknown how a user gets into this state, but a user claimed that even after upgrading to 2.8.6 performing a metadatafile copy from a particular repo to another particular repo failed with:
Content import of /var/lib/pulp/content/units/yum_repo_metadata_file/39/abae87235cc1942704eac508ecd5112de03252b757d8f213fd4aafb4f08488/productid.gz failed - must be an existing file.
The same metadata copy worked fine previously after upgrading to 2.8.6.
This was on a katello server where orphan cleanup is run weekly. Its very possible it was run since the last successful copy.