Project

Profile

Help

Issue #9566

closed

Create better primary keys for subtrees

Added by holger.hees about 1 year ago. Updated 12 months ago.

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

Description

Ticket moved to GitHub: "pulp/pulp_rpm/2304":https://github.com/pulp/pulp_rpm/issues/2304


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

Actions #1

Updated by pulpbot about 1 year ago

  • Status changed from NEW to POST
Actions #3

Updated by dalley about 1 year ago

  • Version deleted (3.3.1)
Actions #5

Updated by dalley 12 months ago

  • Assignee set to dalley
Actions #6

Updated by dalley 12 months ago

  • Triaged changed from No to Yes
Actions #7

Updated by dalley 12 months ago

  • Sprint set to Sprint 111
Actions #8

Updated by fao89 12 months ago

  • Description updated (diff)
  • Status changed from POST to CLOSED - DUPLICATE

Also available in: Atom PDF