Orphan namespaces

Get Help
, ,
1

Hi,

I am in charge of our company collection namespace: wescale.

  • Trying to publish only leads me to a 403 Forbidden error message.
  • Listing my namespaces through https://galaxy.ansible.com/ui/my-namespaces does not show wescale anymore.
  • Investigating details through the Access tab of the namespace does not show any owner.

I tried renewing my ANSIBLE_GALAXY_TOKEN with no success.

I’m looking for help please.

1 Like
2

We are currently investigating some ownership issues to namespaces right now. I’ll mark to check this one and report back when we think it is fix.

2 Likes
3

Thanks for the update.

Same goes for the collection that I also maintain: https://galaxy.ansible.com/ui/repo/published/rtnp/galaxie_clans/

Be strong. Thanks for your efforts. :heart_hands:

1 Like
4

The namespace wescale is back in my kingdom. Thanks a lot!

The second case was not clear enough : the namespace rtnp containing the collection galaxie_clans should be re-attributed to the Galaxy user rtnp.

Thanks again.

2 Likes
5

Awesome! And will get that other one switched back, thanks

1 Like
6

I confirm I got both back at hand. Thanks a lot!

Kudos!

1 Like
7

I’m also missing three namespaces that I had access to. How/who to contact to regain access?

8

We are auditing any mentions in the forum, so mention them here.

Or you can have a ticket opened in the issues.redhat.com epic if you are a customer via support.

Either is fine. We are working to try to resolve all cases we know about ASAP.

1 Like
9

My original namespace tonk is now tonk0 and in my management space I miss

  • ansilabnl
  • ansilab_nl

And I had manager rights on

  • menandmice

Thank you

1 Like
10

@tonk I believe I have fixed all of your namespaces.

2 Likes
11

Hi James,

Yep. They are all back again.

Thank you very much.

1 Like
12

Can you restore the owners to the paloaltonetworks namespace too please? Thanks

1 Like