Project

Profile

Help

Issue #5666

Failed imports leave orphaned artifacts blocking subsequent attempts

Added by ironfroggy over 1 year ago. Updated over 1 year 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:
Quarter:

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.


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 - CURRENTRELEASE

<a title="Actions" class="icon-only icon-actions js-contextmenu" href="#">Actions</a>
Related to Ansible Plugin - Task #6718: Stop using artifacts when importing collectionsCLOSED - CURRENTRELEASE

<a title="Actions" class="icon-only icon-actions js-contextmenu" href="#">Actions</a>

History

#1 Updated by ironfroggy over 1 year ago

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

#2 Updated by daviddavis over 1 year ago

  • Project changed from Pulp to Ansible Plugin

#3 Updated by fao89 about 1 year 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

#4 Updated by fao89 about 1 year ago

  • Related to Task #6718: Stop using artifacts when importing collections added

Please register to edit this issue

Also available in: Atom PDF