Project

Profile

Help

Issue #7495

duplicate key violation, Repository.next_version already exists

Added by awcrosby 18 days ago. Updated 18 days 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:
Q4-2020

Description

We have run into the situation where the my_repo.next_version integer already exists as one of the RepositoryVersion.numbers for my_repo. This causes a duplicate key violation when trying to to call my_repo.new_version()

This has happened twice when using move_content() on a CollectionVersion https://github.com/ansible/galaxy_ng/blob/master/galaxy_ng/app/api/v3/viewsets/collection.py#L268 which uses these tasks https://github.com/ansible/galaxy_ng/blob/master/galaxy_ng/app/tasks/promotion.py, but we don’t have recreation steps at the moment.

I would think this situation would not be possible due to https://github.com/pulp/pulpcore/blob/master/pulpcore/app/models/repository.py#L809, but maybe there is a bug in pulp or non-ideal use of locks in galaxy_ng.

History

#1 Updated by fao89 18 days ago

  • Triaged changed from No to Yes
  • Quarter set to Q4-2020

Please register to edit this issue

Also available in: Atom PDF