Project

Profile

Help

Issue #7246

Story #6134: [EPIC] Pulp import/export

Failed pulp exports leave behind an export file

Added by daviddavis about 1 year ago. Updated about 1 year ago.

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

Description

When an export fails, it still leaves it's tarball on the filesystem. I think we should maybe clean up this file when there's a failure.

Steps to reproduce

  1. Add a raise to a ModelResource or really anywhere late in the export code
  2. Export and observe that the task failed and an export gets created on the filesystem

Associated revisions

Revision 986c3ca2 View on GitHub
Added by ggainey about 1 year ago

Exceptions during export-process will result in incomplete export being removed as cleanup.

fixes #7246

History

#1 Updated by daviddavis about 1 year ago

  • Parent task set to #6134

#2 Updated by fao89 about 1 year ago

  • Triaged changed from No to Yes

#3 Updated by ggainey about 1 year ago

  • Status changed from NEW to ASSIGNED
  • Assignee set to ggainey

#4 Updated by pulpbot about 1 year ago

  • Status changed from ASSIGNED to POST

#5 Updated by ggainey about 1 year ago

  • Status changed from POST to MODIFIED

#6 Updated by bmbouter about 1 year ago

  • Sprint/Milestone set to 3.7.0

#7 Updated by pulpbot about 1 year ago

  • Status changed from MODIFIED to CLOSED - CURRENTRELEASE

Please register to edit this issue

Also available in: Atom PDF