Issue #7220
closed
When a task crashes, the incomplete repo version is not cleaned up and leads to duplicate key error when creating new repo versions
Description
Pulp v3 - rpm plugin
Set up a pulp server on a CentOS 7 host with 4GB of RAM and 4GB of swap.
Configured server to synchronize three RHEL repos (rhel-7-server-rpms,rhel-7-server-optional-rpms, rhel-7-server-extras-rpms).
Synchronization successful for extras and optional - fails when synchronizing the main repo.
The fact that a few of the repos succeeded indicated that the configuration was correct (proper client_ca, client_key, and ca_cert).
Subsequent runs after the failure resulted in the error observed in the attached "duplicate-key-error.json"
I debugged this further and found the failure was most likely caused by running out of memory and swap. Once I increased the available swap (using a local /swapfile) I was able to successfully synchronize.
Files
Related issues
Updated by OnceUponALoop over 4 years ago
Once the swap was increased the issue was not resolved, the duplication error in "duplicate-key-error.json" was still being output anytime a re-synchronization as attempted.
It wasn't until both the repository and the remote were deleted and recreated that I was able to successfully synchronize again.
Updated by dkliban@redhat.com over 4 years ago
When a repository version is not complete and the task associated with that repository version is in a final state, we should be cleaning up the incomplete repository version.
Updated by daviddavis over 4 years ago
- Subject changed from Synchronization Failure due to RAM/Swap exhaustion to When a task crashes, the incomplete repo version is not cleaned up and leads to duplicate key error when creating new repo versions
Updated by dalley about 4 years ago
- Status changed from NEW to CLOSED - DUPLICATE
Thank you! This should be fixed soon.
Updated by dalley about 4 years ago
- Is duplicate of Issue #6463: pulp 3.2.1 duplicate key error when sync added
.