Project

Profile

Help

Issue #5666

closed

Failed imports leave orphaned artifacts blocking subsequent attempts

Added by ironfroggy almost 3 years ago. Updated 11 months 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 #1

Updated by ironfroggy almost 3 years ago

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

Updated by daviddavis almost 3 years ago

  • Project changed from Pulp to Ansible Plugin
Actions #3

Updated by fao89 about 2 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
Actions #4

Updated by fao89 about 2 years ago

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

Updated by pulpbot 11 months ago

  • Description updated (diff)
  • Status changed from NEW to CLOSED - DUPLICATE

Also available in: Atom PDF