Project

Profile

Help

Issue #5666

Failed imports leave orphaned artifacts blocking subsequent attempts

Added by ironfroggy 8 months ago. Updated 8 months ago.

Status:
NEW
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:

Description

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.

History

#1 Updated by ironfroggy 8 months ago

{"errors":[{"status":"400","code":"invalid","title":"Invalid input.","detail":"Artifact already exists."}]}

#2 Updated by daviddavis 8 months ago

  • Project changed from Pulp to Ansible Plugin

Please register to edit this issue

Also available in: Atom PDF