You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 10, 2017. It is now read-only.
Click the 'enable' toggle next to a role named username/xyz
Click the configure widget, and verify the role name is xyz
Wait for role import to succeed (green dot next to 'Succeeded')
Click the 'enable' toggle next to another role named username/something-else
Click the configure widget, and change role name to xyz
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
The text was updated successfully, but these errors were encountered:
Steps to Reproduce
username/xyz
xyz
username/something-else
xyz
Expected Result
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 notxyz
(I think, if I remember correctly).This was discovered when I was adding a
geerlingguy.solr
ansible-container project, while I already had ageerlingguy.solr
ansible role in my user namespace. See: ansible/ansible-container#629The text was updated successfully, but these errors were encountered: