Project

Profile

Help

Actions
Send by e-mail Copy link

Issue #5666

closed

Failed imports leave orphaned artifacts blocking subsequent attempts

Added by ironfroggy about 5 years ago. Updated about 3 years ago.

Status:
CLOSED - DUPLICATE
Priority:
Normal
Assignee:
-
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Platform Release:
OS:
Triaged:
No
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:

Description

Ticket moved to GitHub: "pulp/pulp_ansible/699":https://github.com/pulp/pulp_ansible/issues/699

When an imported is begun and fails, after uploading the artifact and attempting to spawn the import task, the artifact itself is still present. As such, any attempt to publish the same artifact again fails with "Artifact already exists", even though it was never completed successfully and is not available.

Related issues

Related to Pulp - Story #6749: As a core or plugin developer, i want to be able to share temporary files between the viewset and triggered tasksCLOSED - CURRENTRELEASEfao89

Actions
Related to Ansible Plugin - Task #6718: Stop using artifacts when importing collectionsCLOSED - CURRENTRELEASEfao89

Actions
Actions
Send by e-mail Copy link

Also available in: Atom PDF