"Mismatch artifact hash with downloaded file" error when collection resides in rh-certified and community collections

Posted on

AAP Hub version 4.7.1 running on rhel8 virtual machine.

Both the rh-certified and the community repositories are enabled and synced.
ansible.posix versions exist in both repositories.
When our AWX EE is initialized, a custom collection is installed. The galaxy file for this collection has a dependency of ansible.posix v 1.5.1 but the EE initialization fails with the following error:
"Mismatch artifact hash with downloaded file"
Do the artifact hashes differ between the two repositories? If so which one "wins" with the hash?
Follow up question when a specific version of a collection is deleted from aap hub and an attempt is made to upload that version again, is there a way to forcibly upload (either command line or via gui)? I receive the following when attempting to run ansible-galaxy collection publish:
HTTP Code: 400, Message: Artifact already exists Code: invalid

GF

Responses