# Unable to import roles: Role namespace is differ from github organization

**URL:** <https://forum.ansible.com/t/unable-to-import-roles-role-namespace-is-differ-from-github-organization/3336>\
**Category:** Get Help\
**Tags:** galaxy-ng\
**Created:** [January 16, 2024, 1:35pm UTC](https://forum.ansible.com/t/unable-to-import-roles-role-namespace-is-differ-from-github-organization/3336 "2024-01-16T13:35:41Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![oo4abhishek](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/oo4abhishek/32/2004_2.png) [@oo4abhishek](https://forum.ansible.com/u/oo4abhishek)\
**Post date:** [January 16, 2024, 1:35pm UTC](https://forum.ansible.com/t/unable-to-import-roles-role-namespace-is-differ-from-github-organization/3336/1 "2024-01-16T13:35:41Z")

</div>

Hi everybody,

I’m currently experiencing issues importing roles into Galaxy and getting 404 repository not found when importing a role into Galaxy.  
Earlier I used to import roles into

Galaxy namespace (`opstree_devops` ) from the GitHub organization (`ot-osm` ). However, today, when I try to import a role using the details below:

```auto
GitHub Repository: https://github.com/ot-osm/prometheus
Galaxy Namespace: opstree_devops
GitHub Username: oo4abhishek

```

It attempts to import the role from `https://github.com/oo4abhishek/prometheus` , which does not exist. Any insights into this issue would be appreciated.  
For details refer screenshot

 ![galaxyImport](https://us1.discourse-cdn.com/ansible/original/2X/3/30e872fc524b119b81fd6ebf002c65b369b3b184.png)

---

<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:** [January 16, 2024, 2:33pm UTC](https://forum.ansible.com/t/unable-to-import-roles-role-namespace-is-differ-from-github-organization/3336/2 "2024-01-16T14:33:06Z")

</div>

If the repository url is [GitHub - OT-OSM/prometheus](https://github.com/ot-osm/prometheus) then you should be putting “ot-osm” for the “Github user” field.

Currently the [opstree\_devops.prometheus](https://galaxy.ansible.com/ui/standalone/roles/opstree_devops/prometheus/versions/) role is pointed at [https://github.com/opstree\_devops/prometheus](https://github.com/opstree_devops/prometheus) which does not exist either.

If your intent is to import the role from [GitHub - OT-OSM/prometheus](https://github.com/ot-osm/prometheus) into the role fqn opstree\_devops.prometheus, you should use the following values for the import form …

github user: ot-osm  
github repository: prometheus  
namespace name: opstree\_devops  
role name: prometheus

---

<div class="post-metadata">

**Author:** ![oo4abhishek](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/oo4abhishek/32/2004_2.png) [@oo4abhishek](https://forum.ansible.com/u/oo4abhishek)\
**Post date:** [January 17, 2024, 6:01am UTC](https://forum.ansible.com/t/unable-to-import-roles-role-namespace-is-differ-from-github-organization/3336/3 "2024-01-17T06:01:25Z")

</div>

Hi @tannerjc,  
Thanks for the information.  
However, the concern persists. If I use `GitHub user: ot-osm` , it results in a 403 error, stating “Permission denied to import.” Any guidance on resolving this issue would be helpful.

 ![galaxy403](https://us1.discourse-cdn.com/ansible/original/2X/2/23ab359500a202a2f7af017b6ed27113ddf772f4.png)

---

<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:** [January 17, 2024, 1:00pm UTC](https://forum.ansible.com/t/unable-to-import-roles-role-namespace-is-differ-from-github-organization/3336/4 "2024-01-17T13:00:03Z")

</div>

What is your github login that you’ve authenticated to galaxy with?

---

<div class="post-metadata">

**Author:** ![oo4abhishek](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/oo4abhishek/32/2004_2.png) [@oo4abhishek](https://forum.ansible.com/u/oo4abhishek)\
**Post date:** [January 18, 2024, 8:43am UTC](https://forum.ansible.com/t/unable-to-import-roles-role-namespace-is-differ-from-github-organization/3336/5 "2024-01-18T08:43:27Z")

</div>

My login github username is `oo4abhishek`

---

<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:** [January 18, 2024, 2:05pm UTC](https://forum.ansible.com/t/unable-to-import-roles-role-namespace-is-differ-from-github-organization/3336/6 "2024-01-18T14:05:51Z")

</div>

Because “opstree\_devops” is technically the “override” namespace, you are still bound to whatever permissions are set on the “ot-osm” namespace.

[legacy namespace ot-osm](https://galaxy.ansible.com/ui/standalone/namespaces/12807/) did not have a “provider” namespace to control access and therefore your import was denied.

I’ve bound the legacy ot-osm namespace with the v3 provider namespace [ot\_osm](https://galaxy.ansible.com/ui/namespaces/ot_osm/) and then added you as an [owner](https://galaxy.ansible.com/ui/namespaces/ot_osm/?tab=access).

That should theoretically allow you to import roles into the ot-osm namespace, which is a necessary permission even though you are setting an override namespace.