Removal of an Artifact leaves repo with associated artifactless Content forever
Steps to reproduce:
- create repo
- create importer with immediate policy
- remove Artifact by its id, e.g.
Observe no records in
pulp_app_remoteartifact for the deleted Artifact (because of
All the Content-related tables stay untouched => repository claims to have all the content.
Key attributes of deleted Artifact are left in
I don't think that importer is expected to recover from this state with a subsequent sync (e.g. RemoreArtifact doesn't exist for the deleted Artifact, so if this content no longer exists in the upstream repo + sync mode is additive, this artifactless Content will remain in repo.
Workaround: explicitly delete related Content.
Updated by email@example.com about 5 years ago
Did you remove teh Artifact using REST API or directly in the database?
I don't think we want to allow the REST API for deleting Artifacts to support deletion of an Artifact if it belongs to Content that is associated with a repository.