We had some things (namespaces, roles, collections) corrected - probably manually - on the legacy Galaxy instance, in the past (see GitHub ansible/galaxy#2535 ). It looks like the data was attempted to migrate, but the - presumably manual - corrections seem to have caused duplicate namespaces and rol…

The PR got merged and deployed. Branches are captured and exposed now, and the github_user and github_repo fields look correct as well as my installation testing for the related roles.

I’d like to suggest to RedHat personnel responsible for Ansible Galaxy to make the link to the source code repository a user-modifiable project setting. Linking it hard to both GitHub as such and a GitHub namespace identical to the Ansible (role) namespace is not practical. Not with the many except…

Any feedback when this will be fixed? My users cannot install the painless.software role. At least a timeline would be good. :timer_clock:

I have confirmed that the issue being tracked here Loading... and being fixed here github_user should override namespace.name for legacy roles. by jctanner · Pull Request #1923 · ansible/galaxy_ng · GitHub will resolve the painless role installs. (venv) [jtanner@p1 galaxy_ng.legacy_role_mapping]$ r…

Sounds good, thank you! Related to that, what about the branch? Why is the new Gelaxy still resolving to master although github_branch: main is defined in meta/main.yml ?

@bittner good question. I’ll look at that field as well.

Now it works correctly. Thanks for fixing the issue! :+1: $ ansible-galaxy install painless.software Starting galaxy role install process - downloading role 'software', owned by painless - downloading role from https://github.com/painless-software/ansible-role-software/archive/main.tar.gz - extract…

While installing the painless.software role now works, there is still data on the new Galaxy that probably shouldn’t be there or is still not correct. The role painless-software.software should probably be deleted? The role namespace 9580 shows the logo of the GitHub user “painless”, which the “wr…

Data migration to the new galaxy.ansible.com

Get Help

bittner (Peter Bittner) October 3, 2023, 10:20am 2

Similar, if not identical, issue: Namespace issue with new galaxy.ansible.com

Topic		Replies	Views
Roles namespace has changed with the new Galaxy website Get Help galaxy-ng , namespace	9	628	January 8, 2024
Lost namespace's access Get Help galaxy-ng	6	410	October 22, 2023
Please fix my galaxy namespace Get Help galaxy-ng	4	262	August 10, 2024
Namespace issue with new galaxy.ansible.com Get Help galaxy-ng	9	659	November 10, 2023
Namespaces and remotes are messed up since the update Get Help galaxy-ng	6	326	November 9, 2023

Data migration to the new galaxy.ansible.com

Related topics