As part of a release workflow, the newly built collection is published to galaxy but this step produces an error: Run ansible-galaxy collection publish ./$NAMESPACE-$COLLECTION-$NEW_VERSION.tar.gz --api-key=*** ansible-galaxy collection publish ./$NAMESPACE-$COLLECTION-$NEW_VERSION.tar.gz --api-k…

@cloin We’ve deployed a patch that resolves the N namespace problem. I’ve also manually cleaned up your extra namespaces and fixed your account permissions. Please check again.

I added ownership to the correct namespace and fixed the legacynamespace providers accordingly for this list of usernames … [‘wombelix’, ‘Torie-Coding’, ‘fitbeard’, ‘enmanuelmoreira’, ‘jmsierra’, ‘ripclawffb’, ‘andreygubarev’, ‘scareyo’, ‘flowerysong’, ‘yoctoalex’, ‘lowlydba’]

[image] tannerjc: I added ownership to the correct namespace and fixed the legacynamespace providers accordingly for this list of usernames … [‘wombelix’ Thanks a lot, I see my old namespace wombelix again assigned to me :slight_smile: But the wombelix0 namespace also still shows up: [Scr…

Hi, I took another look at the galaxy-ng role namespaces, and it looks like these namespaces belong to me. ( DO1JLR (L3D) · GitHub ). https://galaxy.ansible.com/ui/standalone/namespaces/9259/ https://galaxy.ansible.com/ui/standalone/namespaces/10239/ https://galaxy.ansible.com/ui/standalone/namespace…

Hey, @tannerjc I have experienced the same namespace issue as well. Could you apply the fix to my namespace too? GitHub username: scruffaluff previous correct namespace: scruffaluff new incorrect namespace: scruffaluff0 Thanks for the help!

Hi @tannerjc , I got the same issue with my user robin-checkmk. Also, I got this issue on organization level, if you are able to help there as well: Lost access to namespace `checkmk` on galaxy-ng · Issue #3270 · ansible/galaxy · GitHub Thanks a ton!

Hello @tannerjc Having the same problem. The original namespace is keepersecurity. New one is jwalstra_keeper Company policy changed and I had to use this GitHub account for actual work, and had to rename it. Tried to do a release and got … ERROR! Error when finding available api versions from …

Hello @tannerjc , can you please revert my namespace to its old name also: old: ashleyghooper new: ashleyghooper0

Hi folks, I think i’ve taken care of all the namespace issues brought up in this thread. It’d be helpful for future request to be separate posts, as it’s getting difficult to keep track of this never ending post.

Thank you, but my user DO1JLR is still unable to access these namespaces: https://galaxy.ansible.com/ui/standalone/namespaces/1857/ https://galaxy.ansible.com/ui/standalone/namespaces/1856/ [image] L3D: 1856 (ansible-archive) and 1857 (chaos-bodensee) At least the three dots to opt out of A…

Namespace changed and collection upload not working

Get Help

Topic		Replies	Views
Ansible-Galaxy Namespace Duplicated Collection Namespace Get Help galaxy-ng	18	210	January 15, 2025
Orphan namespaces Get Help galaxy-ng , namespace , bug , paloaltonetworks	11	424	October 6, 2023
Roles namespace has changed with the new Galaxy website Get Help galaxy-ng , namespace	8	637	January 8, 2024
Incorrect namespaces name with 0 Get Help galaxy-ng , collections	4	244	December 12, 2023
Lost namespace's access Get Help galaxy-ng	6	426	October 22, 2023

Namespace changed and collection upload not working

Related topics