Ansible Collections community.general: 403 Forbidden

[Jerome Arellano]

Hello,

Has someone experienced an error when syncing projects?

error encountered:  ERROR! Failed to download collection tar from 'explicit_requirement_community.general' due to the following unforeseen error: <urlopen error Tunnel connection failed: 403 Forbidden>. <urlopen error Tunnel connection failed: 403 Forbidden>

The file requirements.yml created under collections folder in my project directory.

---

collections:

  - name: community.general

    version: 7.4.0

    source: https://galaxy.ansible.com

From the AWX GUI Output, the download is starting however is 403 Forbidden, it somewhat needs some kind of authentication.

Starting galaxy collection install process
Process install dependency map
Starting collection install process
Downloading https://galaxy.ansible.com/api/v3/plugin/ansible/content/published/collections/artifacts/community-general-7.2.0.tar.gz to /var/lib/awx/projects/.__awx_cache/******/stage/tmp/ansible-local-55416g0r_kfh4/tmp1nury9pd/community-general-7.2.0-23jv496b

Do you know any workaround?

[Dick Visser]

Hii

Sounds like something specifically for AWX, so you might get more response on the dedicated AWX list/group...

--
You received this message because you are subscribed to the Google Groups "Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ansible-proje...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/de321e50-770b-4571-bdb9-975f63fd2fd9n%40googlegroups.com.

[Jerome Arellano]

okay, thank you for your response.

[Todd Lewis]

This appears to be serious issues with the galaxy_ng deployment at galaxy.ansible.com. The Ansible Forum's "get help" topic (https://forum.ansible.com/c/help) is blowing up this morning with all sort of things not working, all of which have galaxy.ansible.com in common.

[Matt Martz]

If you have a ~/.ansible/galaxy_token file with a token from the previous deployment, the token will not work with the new deployment, and cause a 403.

To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/7ffa0649-ac95-4f4d-9e8a-2097a6ce6b9en%40googlegroups.com.

--

Matt Martz
@sivel
sivel.net

[Jerome Arellano]

I found a workaround, since I'm not familiar with the ins and outs or modification of ansible configurations inside the k3s pods that I'm using to manage ansible AWX.

we added a source in the requirements.yml of our collections pointing to the old galaxy_ng and it worked.

---

collections:

  - name: community.general

    version: 7.4.0

    source: https://old-galaxy.ansible.com

other workaround mentioned in Skipping Galaxy server https://galaxy.ansible.com/api/ - Get Help - Ansible is adding the galaxy server in your ansible.cfg.

[galaxy] server = https://old-galaxy.ansible.com/

cheers!