https://forum.ansible.com/t/namespace-issue-with-new-galaxy-ansible-com/1325/5

Problem Description: 

Some Role namespaces have been synced to the wrong namespace.

https://forum.ansible.com/t/new-ansible-galaxy/1155/10

bittner[Peter Bittner|https://forum.ansible.com/u/bittner]
 
 
We had some things (namespaces, roles, collections) corrected - probably manually - on the legacy Galaxy instance, in the past (see GitHub ansible/galaxy#2535 2). It looks like the data was attempted to migrate, but the - presumably manual - corrections seem to have caused duplicate namespaces and roles.

See, for example, the role painless.software I maintain:

• Role: “painless.software” → https://galaxy.ansible.com/ui/standalone/roles/painless/software/
• GitHub repository: “painless-software/ansible-role-software” → https://github.com/painless-software/ansible-role-software

Note that the content on the role page of the new Galaxy instance points to a non-existing repository on GitHub, because it assumes the 1:1 mapping of Ansible namespace and GitHub user or org name.

Note that I do not own the “painless” user or org name on GitHub.

The resources now found on Galaxy are:

• Searching in Roles > Role Namespaces for “painless” yields 2 results:
  1. “painless-software” (incorrect namespace, correct icon)
  2. “painless” (correct namespace, incorrect icon → looks like GitHub user “painless”)
• Searching in Collections > Namespaces for “painless” yields only 1 result:
  1. “painless” (correct namespace, correct icon)
  2. (Note: Nothing is found searching for “painless-software”)
• Role “painless-software.software” → https://galaxy.ansible.com/ui/standalone/roles/painless-software/software/ (incorrect namespace, correct icon)
• Role “painless.software” → https://galaxy.ansible.com/ui/standalone/roles/painless/software/ (correct namespace, incorrect icon → looks like GitHub user “painless”)
• Namespace for Roles, “painless-software” → https://galaxy.ansible.com/ui/standalone/namespaces/5371/ (incorrect namespace, correct icon)
• Namespace for Roles, “painless” → https://galaxy.ansible.com/ui/standalone/namespaces/9580/ (correct namespace, incorrect icon → looks like GitHub user “painless”)
• Namespace for Collections, “painless-software” → https://galaxy.ansible.com/ui/namespaces/painless-software/ (404 Not Found → which is correct)
• Namespace for Collections, “painless” → https://galaxy.ansible.com/ui/namespaces/painless/ (correct namespace, correct icon)

Sorry for the plain URLs; as a new user I’m not allowed to have more than 2 URLs in a post.

Also, as a consequence, my users cannot install the painless.software role anymore; it must now be called painless-software.software for the installation to succeed: 

{{$ ansible-galaxy install painless.softwareStarting galaxy role install process

• downloading role 'software', owned by painless
• downloading role from https://github.com/painless/ansible-role-software/archive/master.tar.gz
  [ERROR]: failed to download the file: HTTP Error 404: Not Found
  [WARNING]: - painless.software was NOT installed successfully.
  ERROR! - you can use --ignore-errors to skip failed roles and finish processing the list.}}
  Will this be corrected in an already-planned cleanup task?

Should users report such discrepancies?

—

https://galaxy.ansible.com/ui/task/018af0d4-7664-7054-9169-dca21e3d4945/

Descriptiongit clone for https://github.com/do1jlr/ansible_role_gopass failed
TracebackFile "/venv/lib64/python3.11/site-packages/pulpcore/tasking/tasks.py", line 66, in _execute_task result = func(*args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^ File "/app/galaxy_ng/app/api/v1/tasks.py", line 93, in legacy_role_import raise Exception(f'git clone for {clone_url} failed')

Git is trying to sync from owner_username do1jlr but the provider namespace it actually other https://github.com/roles-ansible/ansible_role_gopassAs you can see in https://old-galaxy.ansible.com/l3d/gopass - the github repo points to the correct provider namespace.

Reminders:

• Set the affected Component(s): Backend, Infrastructure, Pulp, QE, Security, UI
• Apply labels "crc-automation-hub" and/or "private-automation-hub" to indicate if the issue is for Cloud Automation Hub, Private Automation Hub, or both