Description of problem:

When uploading puppet modules to a puppet repository, either through the GUI or using hammer, if there is a file that is not a puppet module, the repo locks. In the task list, it will show into state Paused and Result Failed. If resumed, it will go again to Result Failed.

When trying to upload more modules or deleting the repository to start fresh, it will fail with Could not delete the repository: required lock is already taken by other running tasks. Required lock: read.

One such instance happened by using the pulp-puppet-module-builder, which generates a text file named PULP_MANIFEST in the destination modules dir. Then, when using hammer to upload the content of the puppet modules dir, it will fail because of this text file and go into the locked state.

The only option to unlock it that I've found effective, was to use the foreman-rake console to destroy the paused task. This should not be required. 

Version-Release number of selected component (if applicable):
Satellite 6.2.3

How reproducible:
Whenever uploading (accidentally) a file that is not a puppet module into a puppet repository either through the GUI or using hammer. 

maybe the solution would be to add a conditional statement (both in GUI and hammer) that checks that all files in the modules dir have a .tar.gz extension and fails if it finds anything else?