Dear experts,
In the old version of galaxy I was owner of the namespace “laniakea” for our project roles.
Currently, there are two namespaces “Laniakea-elixir-it”, which is derived from our GitHub organization and “laniakea” the old one. None of them belong to me, also roles versions are not there… This completely breaks our development environment, since it is based on the “laniakea” namespace, while it seems I’m able to use the “Laniakea-elixir-it” one.
This is likely the same issue as the one I reported. See Data migration to the new galaxy.ansible.com
@mtangaro I believe the issue is fixed now.
Lucky you! - Not for everyone, though. Some roles still cannot be installed since the migration.
Hi @tannerjc, thanks a lot for your help.
What I see now is a new “collection namespace” called “laniakea_elixir_it”.
Role installation is till not working, as you can see in the following, because there’s no “laniakea” GitHub repository. And still, I’m not the owner of the neamespaces.
Am I missing some actions to do?
Kind regards,
Marco
(venv2) root@laniakea-dev:~# ansible-galaxy role install Laniakea-elixir-it.galaxy,v2.0.0
Starting galaxy role install process
- downloading role 'galaxy', owned by Laniakea-elixir-it
- downloading role from https://github.com/Laniakea-elixir-it/ansible-role-laniakea-galaxy/archive/v2.0.0.tar.gz
- extracting Laniakea-elixir-it.galaxy to /root/.ansible/roles/Laniakea-elixir-it.galaxy
- Laniakea-elixir-it.galaxy (v2.0.0) was installed successfully
- adding dependency: galaxyproject.cvmfs
- downloading role 'cvmfs', owned by galaxyproject
- downloading role from https://github.com/galaxyproject/ansible-cvmfs/archive/0.2.21.tar.gz
- extracting galaxyproject.cvmfs to /root/.ansible/roles/galaxyproject.cvmfs
- galaxyproject.cvmfs (0.2.21) was installed successfully
(venv2) root@laniakea-dev:~#
(venv2) root@laniakea-dev:~#
(venv2) root@laniakea-dev:~#
(venv2) root@laniakea-dev:~#
(venv2) root@laniakea-dev:~# ansible-galaxy role install laniakea.galaxy,v2.0.0
Starting galaxy role install process
- downloading role 'galaxy', owned by laniakea
- downloading role from https://github.com/laniakea/ansible-role-laniakea-galaxy/archive/v2.0.0.tar.gz
[ERROR]: failed to download the file: HTTP Error 404: Not Found
[WARNING]: - laniakea.galaxy was NOT installed successfully.
ERROR! - you can use --ignore-errors to skip failed roles and finish processing the list.
(venv2) root@laniakea-dev:~#
(venv2) root@laniakea-dev:~#
(venv2) root@laniakea-dev:~# ansible-galaxy role install laniakea.galaxy
Starting galaxy role install process
- downloading role 'galaxy', owned by laniakea
- downloading role from https://github.com/laniakea/ansible-role-laniakea-galaxy/archive/master.tar.gz
[ERROR]: failed to download the file: HTTP Error 404: Not Found
[WARNING]: - laniakea.galaxy was NOT installed successfully.
ERROR! - you can use --ignore-errors to skip failed roles and finish processing the list.
I figured out what is going on with the laniakea/Laniakea-elixir-it. The issue is being tracked here Loading... and the pull request here github_user should override namespace.name for legacy roles. by jctanner · Pull Request #1923 · ansible/galaxy_ng · GitHub
Hi @tannerjc , thanks a lot for fixing. It is working.
(venv2) root@laniakea-dev:~# ansible-galaxy role install laniakea.galaxy,v2.0.0
Starting galaxy role install process
- downloading role 'galaxy', owned by laniakea
- downloading role from https://github.com/Laniakea-elixir-it/ansible-role-laniakea-galaxy/archive/v2.0.0.tar.gz
- extracting laniakea.galaxy to /root/.ansible/roles/laniakea.galaxy
- laniakea.galaxy (v2.0.0) was installed successfully
- adding dependency: galaxyproject.cvmfs
- downloading role 'cvmfs', owned by galaxyproject
- downloading role from https://github.com/galaxyproject/ansible-cvmfs/archive/0.2.21.tar.gz
- extracting galaxyproject.cvmfs to /root/.ansible/roles/galaxyproject.cvmfs
- galaxyproject.cvmfs (0.2.21) was installed successfully
(venv2) root@laniakea-dev:~#
Thanks for the confirmation!
Hi mtangaro,
I have ticked the post by @tannerjc for you this time, but I wanted to make sure you knew about the option to mark a solution so I’m sharing that below. Thank your for letting us know it was fixed for you!
If you get to a point where you consider a post by someone helped you to solve the issue, please tick 
the check-box below their message:
This will mark the message as the solution and show it in the first post for easy access, as well as recognize the person that helped:
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.