# Clarification for namespace from beginner

**URL:** <https://forum.ansible.com/t/clarification-for-namespace-from-beginner/41188>\
**Category:** Get Help\
**Tags:** namespace, ansible-lint, galaxy-ng\
**Created:** [March 22, 2025, 2:35pm UTC](https://forum.ansible.com/t/clarification-for-namespace-from-beginner/41188 "2025-03-22T14:35:15Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![lucas3d](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/lucas3d/32/7606_2.png) [@lucas3d](https://forum.ansible.com/u/lucas3d)\
**Post date:** [March 22, 2025, 2:35pm UTC](https://forum.ansible.com/t/clarification-for-namespace-from-beginner/41188/1 "2025-03-22T14:35:15Z")

</div>

Hi,

I started to publish a few roles on Ansible Galaxy

> **[Ansible Galaxy](https://galaxy.ansible.com/ui/standalone/namespaces/20871)**

Beginner issue:

- Missing validation of my code with ansible-lint
- Missing tag version  
I’m working to resolve these issues.

ansible-lint gives me a warning for the missing namespace in meta/main.yml  
So I add mine “lucasjanin”

> **[Ansible Galaxy](https://galaxy.ansible.com/ui/namespaces/lucasjanin)**

After this, no warning of ansible-lint

```auto
Passed: 0 failure(s), 0 warning(s) on 11 files. Last profile that met the validation criteria was 'production'.

```

But ansible-galaxy import fails:

```auto
===== PROCESSING LOADER RESULTS ====
overriding namespace name via metadata: lucasjanin
legacy namespace lucasjanin does not exist

```

Thanks in advance for any help

---

<div class="post-metadata">

**Author:** ![Edition-X](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/edition-x/32/7963_2.png) [@Edition-X](https://forum.ansible.com/u/Edition-X)\
**Post date:** [March 24, 2025, 11:20am UTC](https://forum.ansible.com/t/clarification-for-namespace-from-beginner/41188/2 "2025-03-24T11:20:38Z")

</div>

Hey, it sounds like you’re bumping into a namespace mismatch. ansible-lint is cool with your custom “lucasjanin” in meta/main.yml since it only checks code style. But Galaxy’s import process is stricter—it expects that legacy namespace to already exist.

Your options are simple:

• **Remove the override:** Let Galaxy use your default account namespace.

• **Register the namespace:** If you really want “lucasjanin”, get it set up as a legacy namespace on Galaxy.

---

<div class="post-metadata">

**Author:** ![lucas3d](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/lucas3d/32/7606_2.png) [@lucas3d](https://forum.ansible.com/u/lucas3d)\
**Post date:** [March 26, 2025, 3:27pm UTC](https://forum.ansible.com/t/clarification-for-namespace-from-beginner/41188/3 "2025-03-26T15:27:26Z")

</div>

Thanks for your clarification!

---

<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:** [April 25, 2025, 3:27pm UTC](https://forum.ansible.com/t/clarification-for-namespace-from-beginner/41188/4 "2025-04-25T15:27:53Z")

</div>

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