# Duplicated namespace, unable to delete old role

**URL:** <https://forum.ansible.com/t/duplicated-namespace-unable-to-delete-old-role/42574>\
**Category:** Get Help\
**Tags:** galaxy-ng\
**Created:** [May 9, 2025, 9:58pm UTC](https://forum.ansible.com/t/duplicated-namespace-unable-to-delete-old-role/42574 "2025-05-09T21:58:05Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![DominiqueFuchs](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/dominiquefuchs/32/8406_2.png) [@DominiqueFuchs](https://forum.ansible.com/u/DominiqueFuchs)\
**Post date:** [May 9, 2025, 9:58pm UTC](https://forum.ansible.com/t/duplicated-namespace-unable-to-delete-old-role/42574/1 "2025-05-09T21:58:05Z")

</div>

Hi everyone,

I’m trying to wrap my head around what happened during the ng transition: I added some updates to a repo with a galaxy role I maintain after a longer time (dominiquefuchs.grafana\_compose). After I realized my role import action fails due to the API key being deactivated, when recreating the key I noticed that there is a duplicate version of my namespace with an old version of that role under a different name (loki\_compose, but namespace appears as DominiqueFuchs, not lowercased).

I tried to delete this old role that became grafana\_compose at some point, but CLI tells me:

```auto
ansible-galaxy role delete DominiqueFuchs loki_compose
Role DominiqueFuchs.loki_compose not found. Maybe it was deleted previously?

```

Not a big deal, but kind of frustrating to have that orphaned, obsolete role namespace lying around with any rights to remove that. I see a lot of posts like these, but most of them seemed to be solved magically behind the scenes. Any tips?

Thanks!

---

<div class="post-metadata">

**Author:** ![samccann](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/samccann/32/18_2.png) [@samccann](https://forum.ansible.com/u/samccann)\
**Post date:** [May 12, 2025, 4:31pm UTC](https://forum.ansible.com/t/duplicated-namespace-unable-to-delete-old-role/42574/2 "2025-05-12T16:31:48Z")

</div>

Hi @DominiqueFuchs - on the surface, yes, this sounds like ‘background magic time’. I’ll take a look later today so see what I can figure out from the galaxy admin view.

---

<div class="post-metadata">

**Author:** ![samccann](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/samccann/32/18_2.png) [@samccann](https://forum.ansible.com/u/samccann)\
**Post date:** [May 13, 2025, 7:17pm UTC](https://forum.ansible.com/t/duplicated-namespace-unable-to-delete-old-role/42574/3 "2025-05-13T19:17:35Z")

</div>

Okay I got rid of the duplicate role and the duplicate role namespace. Let me know if all works well for you now.

---

<div class="post-metadata">

**Author:** ![DominiqueFuchs](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/dominiquefuchs/32/8406_2.png) [@DominiqueFuchs](https://forum.ansible.com/u/DominiqueFuchs)\
**Post date:** [May 13, 2025, 8:04pm UTC](https://forum.ansible.com/t/duplicated-namespace-unable-to-delete-old-role/42574/4 "2025-05-13T20:04:09Z")

</div>

Hi @samccann – looks good now! Thanks for taking the time to look this up and fix it, I appreciate it 🙂

---

<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:** [June 12, 2025, 8:05pm UTC](https://forum.ansible.com/t/duplicated-namespace-unable-to-delete-old-role/42574/5 "2025-06-12T20:05:04Z")

</div>

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