Issue #5521
Updated by pulpbot over 2 years ago
**Ticket moved to GitHub**: "pulp/pulp_ansible/693":https://github.com/pulp/pulp_ansible/issues/693 ---- ### Problem 1\. Upload a collection with \<namespace=foo, name=bar, and version=1.0\> and associate it with a repository_version so it's not an orphan. 2\. Upload a second collection with \<namespace=foo, name=bar, and version=2.0\> and associate it with a repository_version so it's not an orphan. At this point I expect the `/pulp/api/v3/ansible/collection_versions` to show you two CollectionVersions. Once story [5520](https://pulp.plan.io/issues/5520) is implemented you would see exactly 1 Collection (deduplicated since they share Collection. 3\. Now unassociate the version=1.0 collection 4\. Run orphan cleanup and verify the Collection verson=1.0 was deleted from Pulp entirely. Now you'll have 1 Collection and 1 CollectionVersion 5\. Now unassociate the version=2.0 collection 6\. Run orphan cleanup again and verify the Collection version=2.0 was deleted from Pulp entirely. 7\. Now list a Collection using the endpoint from [5520](https://pulp.plan.io/issues/5520) and observe it still shows the Collection even though there are 0 CollectionVersions, this is the bug. ### Solutions Add a [post_delete](https://docs.djangoproject.com/en/2.2/ref/signals/#post-delete) hook on CollectionVersion that will identify if it's the last CollectionVersion referring to that Collection and delete the Collection also if so.