Problem Description:

Some users reported that they are getting namespaces suffixed with numbers, and when trying to upload they have no permissions to upload to the previous namespace.

—

https://forum.ansible.com/t/namespace-changed-and-collection-upload-not-working/1314

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-key=***
shell: /usr/bin/bash -e {0} env:
pythonLocation: /opt/hostedtoolcache/Python/3.11.5/x64
LD_LIBRARY_PATH: /opt/hostedtoolcache/Python/3.11.5/x64/lib
NEW_VERSION: 2.1.14
NAMESPACE: cloin
COLLECTION: eda
ERROR! Error when publishing collection to default (https://galaxy.ansible.com/api/) (HTTP Code: 403, Message: You do not have permission to perform this action. Code: permission_denied)
Publishing collection artifact '/home/runner/work/cloin.eda/cloin.eda/cloin-eda-2.1.14.tar.gz' to default https://galaxy.ansible.com/api/
Error: Process completed with exit code 1.}}

I tried regenerating the token and it failed again.

Upon logging into galaxy and looking at my namespaces, I can see that my namespaces lists “cloin0” instead of “cloin”. “cloin0” is empty. If I navigate to the url for the “cloin” namespace, I see my published collections.

I’m guessing that my publish command fails because I now do not have permissions on the “cloin” namespace, only “cloin0” which I did not create.