# Namespace issue with new galaxy.ansible.com

**URL:** <https://forum.ansible.com/t/namespace-issue-with-new-galaxy-ansible-com/1325>\
**Category:** Get Help\
**Tags:** galaxy-ng\
**Created:** [October 2, 2023, 4:44pm UTC](https://forum.ansible.com/t/namespace-issue-with-new-galaxy-ansible-com/1325 "2023-10-02T16:44:52Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![mtangaro](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mtangaro/32/926_2.png) [@mtangaro](https://forum.ansible.com/u/mtangaro)\
**Post date:** [October 2, 2023, 4:44pm UTC](https://forum.ansible.com/t/namespace-issue-with-new-galaxy-ansible-com/1325/1 "2023-10-02T16:44:52Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![bittner](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/bittner/32/900_2.png) [@bittner](https://forum.ansible.com/u/bittner)\
**Post date:** [October 3, 2023, 10:18am UTC](https://forum.ansible.com/t/namespace-issue-with-new-galaxy-ansible-com/1325/2 "2023-10-03T10:18:25Z")

</div>

This is likely the same issue as the one I reported. See [Data migration to the new galaxy.ansible.com](http://forum.ansible.com/t/data-migration-to-the-new-galaxy-ansible-com/1321)

---

<div class="post-metadata">

**Author:** ![tannerjc](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/tannerjc/32/985_2.png) [@tannerjc](https://forum.ansible.com/u/tannerjc)\
**Post date:** [October 6, 2023, 1:11am UTC](https://forum.ansible.com/t/namespace-issue-with-new-galaxy-ansible-com/1325/3 "2023-10-06T01:11:54Z")

</div>

@mtangaro I believe the issue is fixed now.

---

<div class="post-metadata">

**Author:** ![bittner](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/bittner/32/900_2.png) [@bittner](https://forum.ansible.com/u/bittner)\
**Post date:** [October 6, 2023, 12:10pm UTC](https://forum.ansible.com/t/namespace-issue-with-new-galaxy-ansible-com/1325/4 "2023-10-06T12:10:41Z")

</div>

Lucky you! - Not for everyone, though. Some roles still cannot be installed since the migration.

---

<div class="post-metadata">

**Author:** ![mtangaro](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mtangaro/32/926_2.png) [@mtangaro](https://forum.ansible.com/u/mtangaro)\
**Post date:** [October 6, 2023, 12:52pm UTC](https://forum.ansible.com/t/namespace-issue-with-new-galaxy-ansible-com/1325/5 "2023-10-06T12:52:41Z")

</div>

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

```auto
(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.

```

---

<div class="post-metadata">

**Author:** ![tannerjc](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/tannerjc/32/985_2.png) [@tannerjc](https://forum.ansible.com/u/tannerjc)\
**Post date:** [October 6, 2023, 7:29pm UTC](https://forum.ansible.com/t/namespace-issue-with-new-galaxy-ansible-com/1325/6 "2023-10-06T19:29:10Z")

</div>

I figured out what is going on with the laniakea/Laniakea-elixir-it. The issue is being tracked here [Loading...](https://issues.redhat.com/browse/AAH-2740) and the pull request here [github\_user should override namespace.name for legacy roles. by jctanner · Pull Request #1923 · ansible/galaxy\_ng · GitHub](https://github.com/ansible/galaxy_ng/pull/1923)

---

<div class="post-metadata">

**Author:** ![mtangaro](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mtangaro/32/926_2.png) [@mtangaro](https://forum.ansible.com/u/mtangaro)\
**Post date:** [October 10, 2023, 5:53pm UTC](https://forum.ansible.com/t/namespace-issue-with-new-galaxy-ansible-com/1325/7 "2023-10-10T17:53:51Z")

</div>

Hi @tannerjc , thanks a lot for fixing. It is working.

```auto
(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:~# 

```

---

<div class="post-metadata">

**Author:** ![tannerjc](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/tannerjc/32/985_2.png) [@tannerjc](https://forum.ansible.com/u/tannerjc)\
**Post date:** [October 10, 2023, 6:05pm UTC](https://forum.ansible.com/t/namespace-issue-with-new-galaxy-ansible-com/1325/8 "2023-10-10T18:05:11Z")

</div>

Thanks for the confirmation!

---

<div class="post-metadata">

**Author:** ![Leo](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/leo/32/23_2.png) [@Leo](https://forum.ansible.com/u/Leo)\
**Post date:** [October 11, 2023, 1:05am UTC](https://forum.ansible.com/t/namespace-issue-with-new-galaxy-ansible-com/1325/9 "2023-10-11T01:05:20Z")

</div>

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:

![image](https://us1.discourse-cdn.com/ansible/original/1X/de4bda8ca15f48c52ff19f12b452d10c02126f7f.png)

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:

![image](https://us1.discourse-cdn.com/ansible/original/1X/8964a515490358701e2c80d4ab69712f980e764c.png)

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/ansible/original/1X/1882d9a01da5d8996a862359b0913cc568a39b84.svg) [@system](https://forum.ansible.com/u/system)\
**Post date:** [November 10, 2023, 1:05am UTC](https://forum.ansible.com/t/namespace-issue-with-new-galaxy-ansible-com/1325/10 "2023-11-10T01:05:25Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
