Gracefully handle failed imports

Open
#1,885 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
backend

Research direction

No files, tests, or entry points are named. Start by reviewing the import failure discussion and the linked Redmine issue to define the failure scenarios and expected recovery behavior. Done should mean the handling is specified well enough to prevent a failed import from leaving the Pulp instance in a bad state.

Written by the indexing model from the issue text.

Description

Task

Author: daviddavis (daviddavis)

Redmine Issue: 6567, https://pulp.plan.io/issues/6567

This is mostly a placeholder to discuss how to handle failures during imports. The issue is that a failed import could leave the Pulp instance in a bad state.

Dominant language
Python
Stars
598
Forks
168
Avg merge
1d 4h
Merged PRs (30d)
86

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from pulp/pulpcore

All issues in pulp/pulpcore

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.