Errors with ansible-galaxy and new galaxy.ansible.com token

steadfasterX
Tue, 03 Oct 2023 09:17:34 +0000
Get Help

same issue here, no AWX though! just ansible.

Running Ansible version 2.15.3.

error:

ansible-galaxy collection install --token <token> community.general -vvvvvvvvvvv

ERROR! Error when finding available api versions from release_galaxy (xxxx://galaxy.ansible.com/) (HTTP Code: 403, Message: Forbidden)
ansible-galaxy [core 2.15.3]
config file = /home/xxxxx/.ansible.cfg
configured module search path = [‘/home/xxxxx/.ansible/plugins/modules’, ‘/usr/share/ansible/plugins/modules’]
ansible python module location = /usr/lib/python3.11/site-packages/ansible
ansible collection location = /opt/data/development/git/ansible_collections:/home/xxxxx/.ansible/collections:/usr/share/ansible/collections
executable location = /usr/bin/ansible-galaxy
python version = 3.11.5 (main, Sep 2 2023, 14:16:33) [GCC 13.2.1 20230801] (/usr/bin/python)
jinja version = 3.1.2
libyaml = True
Using /home/xxxxx/.ansible.cfg as config file
Starting galaxy collection install process
Process install dependency map
Initial connection to galaxy_server: xxxx://galaxy.ansible.com/
Created /home/xxxxx/.ansible/galaxy_token
Calling Galaxy at xxxx://galaxy.ansible.com/api/

The file /home/xxxxx/.ansible/galaxy_token is created when not existing and is just empty. Nothing changes when I add this to that file (hope the format is correct):

token: <token>

The <token> has been taken from my NG galaxy profile page (while I see no reason to specify a token when downloading public collections…)

on a second run the output is slightly different as it reads the token file now (which is either empty or filled manually - no it makes no diff in output if one or the other):

ansible-galaxy collection install community.general -vvvvvvvvvvv

ERROR! Error when finding available api versions from release_galaxy (xxxx://galaxy.ansible.com/) (HTTP Code: 403, Message: Forbidden)
ansible-galaxy [core 2.15.3]
config file = /home/xxxxx/.ansible.cfg
configured module search path = [‘/home/xxxxx/.ansible/plugins/modules’, ‘/usr/share/ansible/plugins/modules’]
ansible python module location = /usr/lib/python3.11/site-packages/ansible
ansible collection location = /opt/data/development/git/ansible_collections:/home/xxxxx/.ansible/collections:/usr/share/ansible/collections
executable location = /usr/bin/ansible-galaxy
python version = 3.11.5 (main, Sep 2 2023, 14:16:33) [GCC 13.2.1 20230801] (/usr/bin/python)
jinja version = 3.1.2
libyaml = True
Using /home/xxxxx/.ansible.cfg as config file
Starting galaxy collection install process
Process install dependency map
Initial connection to galaxy_server: https://galaxy.ansible.com/
Opened /home/xxxxx/.ansible/galaxy_token
Calling Galaxy at xxxx://galaxy.ansible.com/api/

I also tried to downgrade/upgrade ansible-core to:

v2.13.9 → same issue

v2.14.1 → same issue

v2.14.5 → same issue

v2.15.4 → same issue

v2.13.5 → python errors incl traceback (if interested I can paste it here but I dont think that matters for this issue here)

2.16.0b1 → same issue

devel (from today, 2023-10-03) → same issue

As I can re-produce the issue on several older Ansible releases I do not think its related to ansible but more to the galaxy api…

5 posts - 2 participants