Cannot import role to galaxy

Get Help
1

Hi,

I wanted to release on galaxy a new version of a legacy ansible role (GitHub - HanXHX/ansible-mysql: Ansible role for Debian : MariaDB (Galera Cluster as option)).

I always have a 403 error.

I tried:

  • On meta/main.yml: Rename my previous namespace (from hanxhx to my real Github user name HanXHX)
  • On meta/main.yml: remove namespace
  • Force alternate branch on ansible-galaxy role import
  • I regened an API key (Ansible Galaxy)
  • Alternate Ansible versions…

Example:

$ ansible-galaxy role import --api-key **** HanXHX ansible-mysql --branch fix_galaxy -vvvv
ansible-galaxy [core 2.17.3]
  config file = None
  configured module search path = ['/home/triplestack/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /home/triplestack/dev/PERSO/ansible-mysql/venv/lib/python3.10/site-packages/ansible
  ansible collection location = /home/triplestack/.ansible/collections:/usr/share/ansible/collections
  executable location = /home/triplestack/dev/PERSO/ansible-mysql/venv/bin/ansible-galaxy
  python version = 3.10.12 (main, Nov 20 2023, 15:14:05) [GCC 11.4.0] (/home/triplestack/dev/PERSO/ansible-mysql/venv/bin/python)
  jinja version = 3.1.4
  libyaml = True
No config file found; using defaults
Initial connection to galaxy_server: https://galaxy.ansible.com
Opened /home/triplestack/.ansible/galaxy_token
Calling Galaxy at https://galaxy.ansible.com/api/
Found API version 'v3, pulp-v3, v1' with Galaxy server default (https://galaxy.ansible.com/api/)
Calling Galaxy at https://galaxy.ansible.com/api/v1/imports/
ERROR! None (HTTP Code: 403, Message: Forbidden)

Issue with my Ansible Galaxy account?

Best,

Emilien

2

In “my namespace” page, I only have hanxhx0… I never use this namespace…

→ Ansible Galaxy

With my nickname i can see 2 namespaces: Ansible Galaxy

Anyone can fix my account please?

3

Any help please?

Thanks!

4

Up? Can you help me please?

5

Good evening,

We have made you the collection owner for that namespace. Please try again now.