Galaxy API returning HTTP Error 500: Internal Server Error when fetching collection artifacts

Get Help
, ,
1

Hello,

The Ansible Galaxy API endpoint is currently returning 500 Internal Server Errors when attempting to download collection tarballs. This is breaking our automated installer pipelines.

Here is the exact stdout trace showing successful dependency resolution but an immediate failure during the artifact download phase:

Downloading https://ansible.com
[ERROR]: Failed to download collection tar from ‘default’: HTTP Error 500: Internal Server Error

The issue occurs consistently across multiple collections (e.g., awx.awx, amazon.aws) and results in non-zero return codes (rc: 1) during ansible-galaxy collection install commands.

2

same here…

3

Hi
This has been escalated inside of Red Hat.

4

Also seeing this — same symptom but different collections (community.proxmox,
community.general), so it’s not scoped to the ones already mentioned above.

One detail that might help narrow it down: the metadata/index endpoint still
works fine, it’s specifically the artifact download that 500s.

Metadata (200 OK):
curl -s “Collection Version – Django REST framework”

Artifact download (500):
curl -sL -w “%{http_code}\n” “https://galaxy.ansible.com/api/v3/plugin/ansible/content/published/collections/artifacts/community-proxmox-2.1.0.tar.gz”

Still reproducing as of this reply.

5

same for me, got patching to do lmao

6

my way to contour this situation was to switch to github method on the requirements.yml

10

ansible galaxy is avaible again for me. Cheers

11

Hi
There was a backend AWS IAM issue, which has been resolved.