Project

Profile

Help

Issue #7030

closed

Pulp does not resync yum metadata files on change

Added by ttereshc about 2 years ago. Updated over 1 year ago.

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

Description

This is for Pulp 3. Since we introduced sync optimizations, the issue we had in Pulp 2 is now also relevant to Pulp 3.

Pulp uses revision numbers in repomd.xml to determine if contents need to be updated on sync. However "modifyrepo" does not generate new revision numbers for non rpm data.

Steps:
1) Setup the following repo

$ mkdir /tmp/my-data
$ cd /tmp/my-data
$ wget https://partha.fedorapeople.org/test-repos/rpm-with-productid/elephant-0.3-0.8.noarch.rpm
$ createrepo .
$ echo "100000" >> productid
$ modifyrepo  --mdtype=productid productid repodata
$ grep revision repodata/repomd.xml
  <revision>1554217257</revision>

2) Sync this repo
3) Now update the repo

$ cd /tmp/my-data
$ echo "100001" >> productid
$ modifyrepo  --mdtype=productid productid repodata
$ grep revision repodata/repomd.xml
  <revision>1554217257</revision>

Notice that the revision number did not change even though a metadata file got updated. Try resyncing this change and notice that the productid change will get ignored.


Related issues

Copied from RPM Support - Issue #4627: Pulp does not resync yum metadata files on changeCLOSED - CURRENTRELEASEttereshcActions
Actions #1

Updated by ttereshc about 2 years ago

  • Copied from Issue #4627: Pulp does not resync yum metadata files on change added
Actions #2

Updated by ttereshc about 2 years ago

  • Description updated (diff)
  • Triaged changed from Yes to No
Actions #3

Updated by dalley about 2 years ago

Is this a known bug with modifyrepo? (or modifyrepo_c which is aliased). If not, maybe we should report it.

Actions #4

Updated by ttereshc about 2 years ago

  • Triaged changed from No to Yes
Actions #5

Updated by ttereshc almost 2 years ago

It's not considered a bug, and, in theory, user can set an arbitrary number for a revision, so it's safer to rely on the checksum :/

Actions #6

Updated by ttereshc almost 2 years ago

  • Sprint set to Sprint 82
Actions #7

Updated by rchan almost 2 years ago

  • Sprint changed from Sprint 82 to Sprint 83
Actions #8

Updated by ppicka over 1 year ago

  • Status changed from NEW to ASSIGNED
  • Assignee set to ppicka
Actions #9

Updated by pulpbot over 1 year ago

  • Status changed from ASSIGNED to POST
Actions #10

Updated by rchan over 1 year ago

  • Sprint changed from Sprint 83 to Sprint 84
Actions #11

Updated by rchan over 1 year ago

  • Sprint changed from Sprint 84 to Sprint 85

Added by ppicka over 1 year ago

Revision f81d7730

Repomd checksum

Check checksum of repomd file (not only revision) to recognize changes is repository metadata files as creatrepo_c doesn't change revision number on change.

closes: #7030 https://pulp.plan.io/issues/7030

Actions #12

Updated by ppicka over 1 year ago

  • Status changed from POST to MODIFIED
Actions #13

Updated by dalley over 1 year ago

  • Sprint/Milestone set to 3.8.0
Actions #14

Updated by pulpbot over 1 year ago

  • Status changed from MODIFIED to CLOSED - CURRENTRELEASE

Also available in: Atom PDF