Project

Profile

Help

Issue #9566

Create better primary keys for subtrees

Added by holger.hees 26 days ago. Updated 8 days ago.

Status:
POST
Priority:
Normal
Assignee:
-
Sprint/Milestone:
-
Start date:
11/12/2021
Due date:
Estimated time:
Severity:
2. Medium
Version:
Platform Release:
OS:
Triaged:
No
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:

Description

Scenario:

My primary pulp instance is hosting 2 distributions of the same repository (like staging and production) which are referencing different versions of the same repository. During my initial run, both distributions are point to version 1. So far so good.

Now I have a secondary pulp instance which is mirroring the 2 primary distributions by creating separate remotes and repositories.

The repository on the primary node contains now a subtree which is identically in version 1 for staging and production. Means it has the same hash.

Now, during the sync process the metadata for this subtree are stored by createing a primary key like "{repodata}-{treeinfo['hash']}". This collides with staging and production, because contentwise and with the hash, the subtree is the same for both staging and production. The key should be something like "{repodata}-{treeinfo['hash']}-{repository_pk}"

https://github.com/pulp/pulp_rpm/pull/2173

History

#1 Updated by pulpbot 24 days ago

  • Status changed from NEW to POST

#3 Updated by dalley 8 days ago

  • Version deleted (3.3.1)

Please register to edit this issue

Also available in: Atom PDF