# Two namespaces with same name on Galaxy NG

**URL:** <https://forum.ansible.com/t/two-namespaces-with-same-name-on-galaxy-ng/2670>\
**Category:** Get Help\
**Tags:** bug, galaxy-ng\
**Created:** [November 30, 2023, 1:38pm UTC](https://forum.ansible.com/t/two-namespaces-with-same-name-on-galaxy-ng/2670 "2023-11-30T13:38:52Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Branlute](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/branlute/32/1677_2.png) [@Branlute](https://forum.ansible.com/u/Branlute)\
**Post date:** [November 30, 2023, 1:38pm UTC](https://forum.ansible.com/t/two-namespaces-with-same-name-on-galaxy-ng/2670/1 "2023-11-30T13:38:53Z")

</div>

Hello,

After Galaxy NG release there are two namespaces for our Org.

Original namespace: STEAMULO  
New namespace: steamulo

On the Ansible Galaxy website, there are two namespaces : [Ansible Galaxy](https://galaxy.ansible.com/ui/standalone/namespaces/6620/)  
[Ansible Galaxy](https://galaxy.ansible.com/ui/standalone/namespaces/9892/)

But we can manage only the seconde one (steamulo).  
When we upload a new version of roles, it’s not available on the new namespace.

Can you delete the old one “STEAMULO”, or merge the two namespaces ?

---

<div class="post-metadata">

**Author:** ![agarov](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/agarov/32/1679_2.png) [@agarov](https://forum.ansible.com/u/agarov)\
**Post date:** [January 30, 2024, 8:53am UTC](https://forum.ansible.com/t/two-namespaces-with-same-name-on-galaxy-ng/2670/2 "2024-01-30T08:53:34Z")

</div>

Hello,

We still face the same problem.

Can you please provide any fix ?

Thank you

---

<div class="post-metadata">

**Author:** ![MonolithProjects](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/monolithprojects/32/1014_2.png) [@MonolithProjects](https://forum.ansible.com/u/MonolithProjects)\
**Post date:** [March 12, 2024, 9:58pm UTC](https://forum.ansible.com/t/two-namespaces-with-same-name-on-galaxy-ng/2670/3 "2024-03-12T21:58:04Z")

</div>

I can confirm that this issue still exist in galaxy-ng. Now i have Role namespace called `MonolithProjects` and also `monolithprojects`. The new releases of the Roles are being uploaded to `monolithprojects` but Galaxy UI is always pointing to `MonolithProjects`. Can someone please fix this so we can have only our original namespaces (in my case it is `MonolithProjects` [Ansible Galaxy](https://galaxy.ansible.com/ui/standalone/namespaces/9446/?page=1&page_size=10&sort=-created&keywords=github_actions_runner)

---

<div class="post-metadata">

**Author:** ![agarov](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/agarov/32/1679_2.png) [@agarov](https://forum.ansible.com/u/agarov)\
**Post date:** [October 10, 2024, 1:30pm UTC](https://forum.ansible.com/t/two-namespaces-with-same-name-on-galaxy-ng/2670/4 "2024-10-10T13:30:33Z")

</div>

Is it possible to have a return from the ansible galaxy team on this subject please ?

it’s been almost a year and we still can’t manage our organization because of the migration … It doesn’t make you want to use Ansible Galaxy and rather rely on github

---

<div class="post-metadata">

**Author:** ![chynasan](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/chynasan/32/1022_2.png) [@chynasan](https://forum.ansible.com/u/chynasan)\
**Post date:** [October 15, 2024, 7:35pm UTC](https://forum.ansible.com/t/two-namespaces-with-same-name-on-galaxy-ng/2670/5 "2024-10-15T19:35:24Z")

</div>

This is something that a user with the namespace owner role can delete, so any user in the [admin list here](https://galaxy.ansible.com/ui/namespaces/steamulo/?tab=access), for steamulo.

You can use curl to delete the [STEAMULO (all caps)](https://galaxy.ansible.com/api/v1/namespaces/6620/) instance like this:

`curl -X DELETE -H 'Authorization: token <API token>' https://galaxy.ansible.com/api/v1/namespaces/6620/`

I tested and confirmed in a staging environment that this cascade deleted STEAMULO while leaving steamulo in tact.

The [API user guide documentation](https://ansible.readthedocs.io/projects/galaxy-ng/en/latest/community/userguide/) doesn’t outline this exact scenario, but can guide you further if you need help with generating an API token.