Deleting a collection version from crc AH returns a 502

Description

When deleting a collection from the staging repository, there are 2 deletion options. Delete from System and Delete from Repo. ansible.netcommon had a failure in it that needed to be addressed but was not a code change (aka no version bump was needed from a semver perspective) so we elected to delete it from AH and reupload the version with the changes. 

 

When I attempted to delete the version (5.1.2) from staging, I elected to go from the system as that was the closest to the previous workflow and the version needed to be purged from the entire system. This returned a 502 the first time, then when I came back about 10 minutes or so (502 is generally a resource issue so I assumed the system was backed up for any number of reasons) it then returned a 404. I asked my colleague alhart@redhat.com to confirm my findings. She was able to delete but from the repo only.

 

While we have now learned that we aren't able to upload due to some back end pulp things, this report is mainly to report the 502 and then subsequent 404.

Key Dependency Versions

{"available_versions":\{"v3":"v3/","pulp-v3":"pulp/api/v3/"}

,"server_version":"4.8.0dev","galaxy_ng_version":"4.8.0dev","galaxy_ng_commit":"origin/master:a314e11","galaxy_importer_version":"0.4.10","pulp_core_version":"3.23.4","pulp_ansible_version":"0.17.2","pulp_container_version":"2.14.5"}

Steps to Reproduce

select the specific version in AH approval dashboard but just clicking the version which is hyperlinked to the version view in staging, then triple dots in the top right to edit the version/collection. 

Selected from delete from system, returned a 502. Waited a bit then hit system again and got a 404, verified it was still there in queue so hit repo in case the system one did propagate/go through given the 502 then 404 response.

Actual Behavior

Version was deleted from system and same version/artifact was able to be uploaded again.

Expected Behavior

Returned a 502 then a 404 after another attempt. Was able to be removed via repo selection eventually with no issue.