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:
-
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 wrote:
> This appears to be serious issues with the galaxy_ng deployment at
> galaxy.ansible.com. The
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, 20
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
> wrote:
>
>> Hello,
>>
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
wrote:
> Hello,
>
> Has someone experienced an error when syncing projects?
>
> error encountered:
> *ERROR! Failed to download collecti
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: . *
The file requirements.yml created under collections folder in my project
direct
