Project

Profile

Help

Issue #7918

FilesystemExporter does not gracefully handle exporting multiple times

Added by daviddavis 8 months ago. Updated 8 months ago.

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

The move to GHA exposed this bug (not sure how it wasn't an issue in Travis but I was able to reproduce locally).

If there are pre-existing files in the location that FileSystem attempts to export to you get a FileExistsError. This is common in the case where you're exporting multiple times.

Some potential solutions:

  1. Check that the directory is empty before exporting. Maybe even refuse to export but have a --force flag that will remove files in this directory.
  2. Ignore file exists errors either silently or raise a warning.

Related issues

Related to Pulp - Task #7890: Unskip broken filesystem exporter testCLOSED - CURRENTRELEASE

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

History

#1 Updated by daviddavis 8 months ago

  • Related to Task #7890: Unskip broken filesystem exporter test added

#2 Updated by fao89 8 months ago

  • Triaged changed from No to Yes

#3 Updated by ipanova@redhat.com 8 months ago

I would ignore file exists error. If with every export we expect an additive mode, it would be a waste to --force remove existing file so just in a later step place them back.

Please register to edit this issue

Also available in: Atom PDF