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

Can't delete roles using Web UI for repos that don't exist/have been renamed #187

Closed
emonty opened this issue Sep 6, 2016 · 7 comments
Closed

Comments

@emonty
Copy link

emonty commented Sep 6, 2016

https://galaxy.ansible.com/openstack-infra/puppet/ is a role in galaxy that was imported in February from the repo openstack-infra/ansible-puppet. Since then, that repo has been renamed to openstack-infra/ansible-role-puppet to be more inline with the ansible-role-$foo naming scheme. However, I can't import openstack-infra/ansible-role-puppet to openstack-infra.puppet because there is already something there - and I can't delete it because the role management page only shows repos that exists since it's driven by looking at the list of repos you have access to.

Short term - could someone delete that role for me? Long term - can we make a mechanism to allow deleting roles that no longer have valid github repos?

@c-mart
Copy link

c-mart commented Sep 12, 2016

I also cannot delete this role from Galaxy that I created for testing, and then deleted the source repository.

screenshot_2016-09-12_16-26-45

I click the red DELETE button and nothing happens.

@chouseknecht
Copy link
Contributor

We could probably automate this with a background task that deletes Galaxy roles that no longer exist GitHub.

  • openstack-infra.puppet role is deleted.
  • cyverse-ansble.hello-test is deleted

@chouseknecht
Copy link
Contributor

  • Added a background task that removes roles where the GitHub repository is no longer accessible and updates roles where the GitHub repository has been renamed.
  • The refresh process in the UI (on My Roles page) also removes user roles where the repository is no longer accessible and updates roles when the repository name has changed.
  • When deleting a role through the UI, the process now traps the error that occurs when the repository was previously deleted. When this happens the user is notified that they need to click the Refresh button. And as mentioned above, the refresh process will remove any roles where the GitHub repo cannot be accessed and update roles with the correct repository name when the repository name has changed.

Marking as closed. However, if the error persists, please re-open.

@chouseknecht
Copy link
Contributor

@emonty - btw, the puppet role is no longer. It has been removed from the database as well.

@c-mart the hello-test role has been completely removed.

@alpegon
Copy link

alpegon commented Nov 7, 2016

Hi, several days ago I've created a role called https://galaxy.ansible.com/grycap/rol-nfs/ based on the github repo https://github.com/grycap/ansible-rol-nfs.
As you realize the name is incorrect (rol instead of role), so I've modified the github project and changed the name to https://github.com/grycap/ansible-role-nfs.
Now I have two projects in the main page of the organization: https://galaxy.ansible.com/grycap/:

Both of them point to the same github repo (the modified one https://github.com/grycap/ansible-role-nfs).
The problem is that old github project (rol-nfs) doesn't apper under 'my roles ' project list and I cannot delete or modify it.

I've also tried to update the project list but when I click on the refresh button in my roles page, the refresh keeps running forever.

Could someone check this behaviour please?
Thank you very much

@alpegon
Copy link

alpegon commented Nov 9, 2016

Ok, I've deleted the role grycap/ansible-role-nfs from ansible galaxy and both of the organization roles disappeared.
Problem solved.

@skuark
Copy link

skuark commented Nov 14, 2016

Hi. I am experiencing a similar issue after renaming some ansible role repositories on GitHub. I can't re-import neither delete old ones. The problematic repos are in the profile https://galaxy.ansible.com/dlcoder/

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

5 participants