Unable to correct namespace

[michaelrigart]

Bug Report

SUMMARY

My Galaxy namespace is different from my GitHub username. This results in difficulties syncing playbooks to Galaxy and performing other administrative tasks on Ansible Galaxy.

STEPS TO REPRODUCE

1. Log in Ansible Galaxy using my GH account (username: michaelrigart)
2. Go to My Content -> Edit Namespace
3. Unable to remove the wrong namespace
4. Unable to add the correct namespace

EXPECTED RESULTS

Should be able to replace the wrong namespace with the correct one.

ACTUAL RESULTS

1. While removing the wrong namespace, nothing seems to happen

2. Adding the correct namespace and trying to save results in an error message

[thedoubl3j]

hey @michaelrigart I am going to play around with your namespace for a second, when the process of creating these comes from the auto generated user auth, things can get mangled. note the playing around will involve changing some things around so I would hold off for a bit on pushing/pulling anything from it. worst comes to worst we can investigate a new namespace since you only have roles.

(close by mistake)

[michaelrigart]

Hi @thedoubl3j ,

no problem. Go ahead.

[thedoubl3j]

@michaelrigart so my testing didn't lead to a solution the ways things currently stand. my guess is that somehow the front end won't let go of the reference of the old provider namespace and I don't have access to the stuff on the backend so I can't confirm where the issue lies.

Immediate resolution is that we could create a namespace that is your username now with lower case as that should be allowed given it doesn't exist and the old one exists in the old "rule set". It would not cause collection collision via naming since your current namespace can't house them due to the capital letters. My only concern and this would probably need some testing from you would be role collision with the old namespace. I would say add the same roles currently there and make a noticeable change (like drop a test note in the readme or something) and then see if we are getting the correct one we want. namespaces previous to collections (though the concept didn't really exist then) I believe we flattened before queried for a role so that is my cause for concern currently.

The other path we could take which is not very ideal is that we could look at attempting to edit the namespace on the backend (most likely in the DB) and just nuke that provider namespace. While this is the most ideal because it is straight forward, I don't think it will have much bite given our timeline of moving to galaxy_ng (beta banner should be coming up sometime this week or next) and this kind of edit takes time away from keeping that deployment on schedule.

Either way, I will file a bug on the galaxy JIRA that I will link here this week to see if we can get it investigated to make sure it doesn't have a reproducer in galaxy_ng. If I don't drop it here soon ish (this week) ping me again and I will get it in. The jira is publicly viewable so you can comment or just see triage happen (if you care).