Actions
Issue #5666
closed
Failed imports leave orphaned artifacts blocking subsequent attempts
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
Updated by ironfroggy about 5 years ago
{"errors":[{"status":"400","code":"invalid","title":"Invalid input.","detail":"Artifact already exists."}]}
Updated by daviddavis about 5 years ago
- Project changed from Pulp to Ansible Plugin
I confirmed that this problem is specific to pulp_ansible. In pulpcore, we reuse any existing artifact:
It looks like the behavior is different for pulp_ansible:
Updated by fao89 over 4 years ago
- Related to Story #6749: As a core or plugin developer, i want to be able to share temporary files between the viewset and triggered tasks added
Updated by fao89 over 4 years ago
- Related to Task #6718: Stop using artifacts when importing collections added
Updated by pulpbot about 3 years ago
- Description updated (diff)
- Status changed from NEW to CLOSED - DUPLICATE
Actions
.