Project

Profile

Help

Actions
Send by e-mail Copy link

Issue #7246

closed

Story #6134: [EPIC] Pulp import/export

Failed pulp exports leave behind an export file

Added by daviddavis over 4 years ago. Updated about 4 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
ggainey
Category:
-
Sprint/Milestone:
3.7.0
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
Actions
Copy link
 #1

Updated by daviddavis over 4 years ago

  • Parent issue set to #6134
Actions
Copy link
 #2

Updated by fao89 over 4 years ago

  • Triaged changed from No to Yes
Actions
Copy link
 #3

Updated by ggainey over 4 years ago

  • Status changed from NEW to ASSIGNED
  • Assignee set to ggainey
Actions
Copy link
 #4

Updated by pulpbot over 4 years ago

  • Status changed from ASSIGNED to POST

Added by ggainey over 4 years ago

Revision 986c3ca2 | View on GitHub

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

fixes #7246

Actions
Copy link
 #5

Updated by ggainey over 4 years ago

  • Status changed from POST to MODIFIED
Actions
Copy link
 #6

Updated by bmbouter about 4 years ago

  • Sprint/Milestone set to 3.7.0
Actions
Copy link
 #7

Updated by pulpbot about 4 years ago

  • Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Actions
Send by e-mail Copy link

Also available in: Atom PDF