Skip to content
This repository was archived by the owner on Nov 10, 2017. It is now read-only.

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

Closed
geerlingguy opened this issue Jul 5, 2017 · 2 comments
Assignees
Milestone

Comments

@geerlingguy
Copy link

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

@cutwater
Copy link
Collaborator

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

@chouseknecht
Copy link
Contributor

This issue was moved to ansible/galaxy#47

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants