# Bot used for publishing has lost namespace access **URL:** \ **Category:** Get Help\ **Tags:** bug, namespace, bot, galaxy-ng\ **Created:** [October 4, 2023, 7:29pm UTC](https://forum.ansible.com/t/bot-used-for-publishing-has-lost-namespace-access/1413 "2023-10-04T19:29:52Z")\ **Posts on this page:** 17\ **Page:** 1
**Author:** ![cidrblock](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/cidrblock/32/126_2.png) [@cidrblock](https://forum.ansible.com/u/cidrblock)\ **Post date:** [October 4, 2023, 7:29pm UTC](https://forum.ansible.com/t/bot-used-for-publishing-has-lost-namespace-access/1413/1 "2023-10-04T19:29:52Z")
Hey all- We use a bot and it seems to have lost access to all of the namepsaces it could publish to. Can the namespace list for “ansibuddy” be restored to what it was on old galaxy? Thanks, Brad ---
**Author:** ![felixfontein](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/felixfontein/32/7530_2.png) [@felixfontein](https://forum.ansible.com/u/felixfontein)\ **Post date:** [October 4, 2023, 8:30pm UTC](https://forum.ansible.com/t/bot-used-for-publishing-has-lost-namespace-access/1413/2 "2023-10-04T20:30:54Z")
Since some planned community collection released are coming up soon (i.e. this weekend / next Monday), it would be really great if this could be fixed soon. ---
**Author:** ![felixfontein](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/felixfontein/32/7530_2.png) [@felixfontein](https://forum.ansible.com/u/felixfontein)\ **Post date:** [October 5, 2023, 7:47pm UTC](https://forum.ansible.com/t/bot-used-for-publishing-has-lost-namespace-access/1413/3 "2023-10-05T19:47:36Z")
@rochacbruno - do you know who can help with this? This is rather urgent, since Ansible 8.5.0 is coming up next week and several collections that should be part of it need to be released. ---
**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:** [October 6, 2023, 2:09am UTC](https://forum.ansible.com/t/bot-used-for-publishing-has-lost-namespace-access/1413/4 "2023-10-06T02:09:01Z")
I believe I have just fixed the ansibuddy account. ---
**Author:** ![jooola](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/jooola/32/737_2.png) [@jooola](https://forum.ansible.com/u/jooola)\ **Post date:** [October 6, 2023, 2:30pm UTC](https://forum.ansible.com/t/bot-used-for-publishing-has-lost-namespace-access/1413/5 "2023-10-06T14:30:22Z")
Not sure if this is related, but we are still having some issue to release our collection: [Zuul](https://ansible.softwarefactory-project.io/zuul/build/040b96db82e44fd4aaf3f6728afc1a88) ---
**Author:** ![cidrblock](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/cidrblock/32/126_2.png) [@cidrblock](https://forum.ansible.com/u/cidrblock)\ **Post date:** [October 6, 2023, 3:08pm UTC](https://forum.ansible.com/t/bot-used-for-publishing-has-lost-namespace-access/1413/6 "2023-10-06T15:08:03Z")
Thanks @tannerjc We’ve published cisco.nxos and ansible.scm. Waiting to mark as solved until we hit a few more namespaces. -brad ---
**Author:** ![KB-perByte](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/kb-perbyte/32/541_2.png) [@KB-perByte](https://forum.ansible.com/u/KB-perByte)\ **Post date:** [October 6, 2023, 3:21pm UTC](https://forum.ansible.com/t/bot-used-for-publishing-has-lost-namespace-access/1413/7 "2023-10-06T15:21:56Z")
We published the cisco.ios collection, the issue looks resolved. Thanks @tannerjc and @cidrblock ---
**Author:** ![felixfontein](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/felixfontein/32/7530_2.png) [@felixfontein](https://forum.ansible.com/u/felixfontein)\ **Post date:** [October 6, 2023, 7:21pm UTC](https://forum.ansible.com/t/bot-used-for-publishing-has-lost-namespace-access/1413/8 "2023-10-06T19:21:04Z")
I also just was able to publish community.internal\_test\_tools via Zuul, it worked fine! Thanks a lot everyone! 🎉 ---
**Author:** ![jillr](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/jillr/32/2752_2.png) [@jillr](https://forum.ansible.com/u/jillr)\ **Post date:** [October 6, 2023, 8:11pm UTC](https://forum.ansible.com/t/bot-used-for-publishing-has-lost-namespace-access/1413/9 "2023-10-06T20:11:24Z")
The publishing job should be working again. You can retag the release to trigger the pipeline, or if you prefer I can manually publish hetzner.hcloud 2.1.2. ---
**Author:** ![jooola](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/jooola/32/737_2.png) [@jooola](https://forum.ansible.com/u/jooola)\ **Post date:** [October 9, 2023, 9:50am UTC](https://forum.ansible.com/t/bot-used-for-publishing-has-lost-namespace-access/1413/10 "2023-10-09T09:50:38Z")
Hey, if you can trigger the release pipeline for this tag or release it yourself, it would be awesome! Thanks! ---
**Author:** ![jillr](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/jillr/32/2752_2.png) [@jillr](https://forum.ansible.com/u/jillr)\ **Post date:** [October 12, 2023, 10:50pm UTC](https://forum.ansible.com/t/bot-used-for-publishing-has-lost-namespace-access/1413/11 "2023-10-12T22:50:29Z")
@tannerjc Apologies, looks like we also need the hetzner namespace added to the ansibuddy user when you have a chance. Thank you for working through these!! ---
**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:** [October 13, 2023, 1:34pm UTC](https://forum.ansible.com/t/bot-used-for-publishing-has-lost-namespace-access/1413/12 "2023-10-13T13:34:38Z")
@jillr I added ansibuddy as an owner of the hetzner namespace. The current owners are … ```auto >>> rbac.get_v3_namespace_owners(hetzner) [, , , , , , ] ``` ---
**Author:** ![jillr](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/jillr/32/2752_2.png) [@jillr](https://forum.ansible.com/u/jillr)\ **Post date:** [October 13, 2023, 3:53pm UTC](https://forum.ansible.com/t/bot-used-for-publishing-has-lost-namespace-access/1413/13 "2023-10-13T15:53:22Z")
[https://galaxy.ansible.com/ui/repo/published/hetzner/hcloud/?version=2.1.2](https://galaxy.ansible.com/ui/repo/published/hetzner/hcloud/?version=2.1.2) You should be all set now ---
**Author:** ![jooola](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/jooola/32/737_2.png) [@jooola](https://forum.ansible.com/u/jooola)\ **Post date:** [October 13, 2023, 4:04pm UTC](https://forum.ansible.com/t/bot-used-for-publishing-has-lost-namespace-access/1413/14 "2023-10-13T16:04:36Z")
Great! Thanks a lot for the work! ---
**Author:** ![jooola](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/jooola/32/737_2.png) [@jooola](https://forum.ansible.com/u/jooola)\ **Post date:** [October 30, 2023, 7:49am UTC](https://forum.ansible.com/t/bot-used-for-publishing-has-lost-namespace-access/1413/15 "2023-10-30T07:49:43Z")
@jillr Maybe this is unrelated to this thread, but it seems another of our releases could not be published to Ansible Galaxy because of some permission issues, could you or someone else take a look please ? [https://ansible.softwarefactory-project.io/zuul/build/b02a2cbabf6d4113a9a69654a0998cf8](https://ansible.softwarefactory-project.io/zuul/build/b02a2cbabf6d4113a9a69654a0998cf8) ---
**Author:** ![jillr](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/jillr/32/2752_2.png) [@jillr](https://forum.ansible.com/u/jillr)\ **Post date:** [October 30, 2023, 4:04pm UTC](https://forum.ansible.com/t/bot-used-for-publishing-has-lost-namespace-access/1413/16 "2023-10-30T16:04:55Z")
I expect you may have run into the same problem another collection did last week, which would have been resolved by [Re-encrypt galaxy token for ansibuddy by jillr · Pull Request #531 · ansible/zuul-config · GitHub](https://github.com/ansible/zuul-config/pull/531). I’ve manually uploaded 2.2.0 for you to galaxy. ---
**Author:** ![system](https://us1.discourse-cdn.com/ansible/original/1X/1882d9a01da5d8996a862359b0913cc568a39b84.svg) [@system](https://forum.ansible.com/u/system)\ **Post date:** [November 29, 2023, 4:05pm UTC](https://forum.ansible.com/t/bot-used-for-publishing-has-lost-namespace-access/1413/17 "2023-11-29T16:05:41Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.