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.

On Mon, Oct 2, 2023 at 10:43 AM Todd Lewis <[email protected]> wrote:

> 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.
>
> On Monday, October 2, 2023 at 5:51:44 AM UTC-4 Jerome Arellano wrote:
>
>> okay, thank you for your response.
>>
>> On Monday, October 2, 2023 at 9:35:20 AM UTC+2 Dick Visser wrote:
>>
>>> Hii
>>> Sounds like something specifically for AWX, so you might get more
>>> response on the dedicated AWX list/group...
>>>
>>> On Mon, 2 Oct 2023 at 09:19, Jerome Arellano <[email protected]>
>>> wrote:
>>>
>>>> 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?
>>>>
>>>> --
>>>> 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 [email protected].
>>>> To view this discussion on the web visit
>>>> https://groups.google.com/d/msgid/ansible-project/de321e50-770b-4571-bdb9-975f63fd2fd9n%40googlegroups.com
>>>> <https://groups.google.com/d/msgid/ansible-project/de321e50-770b-4571-bdb9-975f63fd2fd9n%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>> .
>>>>
>>> --
> 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 [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/ansible-project/7ffa0649-ac95-4f4d-9e8a-2097a6ce6b9en%40googlegroups.com
> <https://groups.google.com/d/msgid/ansible-project/7ffa0649-ac95-4f4d-9e8a-2097a6ce6b9en%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>


-- 
Matt Martz
@sivel
sivel.net

-- 
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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAD8N0v9ASmk5BJLE%2BwYw0bNDc%3D92PtW4s2aqoV8FQ4cf3fzAcg%40mail.gmail.com.

Reply via email to