No error when adding a new role/container project that has the same name as an existing project

[chouseknecht]

From @geerlingguy on July 5, 2017 21:26

Steps to Reproduce

1. Visit 'roleadd' on Ansible Galaxy (https://galaxy.ansible.com/roleadd#/)
2. Click the 'enable' toggle next to a role named username/xyz
3. Click the configure widget, and verify the role name is xyz
4. Wait for role import to succeed (green dot next to 'Succeeded')
5. Click the 'enable' toggle next to another role named username/something-else
6. Click the configure widget, and change role name to xyz
7. Click 'Save' and observe the result.

Expected Result

• I should see an error message alerting me that a role with that name already exists in my Galaxy namespace.

Actual Result

The 'Running' status widget keeps spinning forever, and nothing seems to happen. After a while, if you refresh the page, you can see the project was imported as something-else and not xyz (I think, if I remember correctly).

This was discovered when I was adding a geerlingguy.solr ansible-container project, while I already had a geerlingguy.solr ansible role in my user namespace. See: ansible/ansible-container#629

Copied from original issue: ansible/galaxy-issues#270

[chouseknecht]

From @cutwater on October 10, 2017 18:8

@geerlingguy I cannot reproduce this issue neither on http://galaxy.ansible.com, nor on latest development branch. Please confirm if it's still valid.