Project

Profile

Help

Issue #7030

Pulp does not resync yum metadata files on change

Added by ttereshc 6 months ago. Updated 22 days 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 - CURRENTRELEASE<a title="Actions" class="icon-only icon-actions js-contextmenu" href="#">Actions</a>

Associated revisions

Revision f81d7730 View on GitHub
Added by ppicka 25 days ago

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

History

#1 Updated by ttereshc 6 months ago

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

#2 Updated by ttereshc 6 months ago

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

#3 Updated by dalley 6 months ago

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

#4 Updated by ttereshc 5 months ago

  • Triaged changed from No to Yes

#5 Updated by ttereshc 4 months 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 :/

#6 Updated by ttereshc 2 months ago

  • Sprint set to Sprint 82

#7 Updated by rchan 2 months ago

  • Sprint changed from Sprint 82 to Sprint 83

#8 Updated by ppicka about 2 months ago

  • Status changed from NEW to ASSIGNED
  • Assignee set to ppicka

#9 Updated by pulpbot about 2 months ago

  • Status changed from ASSIGNED to POST

#10 Updated by rchan about 2 months ago

  • Sprint changed from Sprint 83 to Sprint 84

#11 Updated by rchan about 1 month ago

  • Sprint changed from Sprint 84 to Sprint 85

#12 Updated by ppicka 25 days ago

  • Status changed from POST to MODIFIED

#13 Updated by dalley 22 days ago

  • Sprint/Milestone set to 3.8.0

#14 Updated by pulpbot 22 days ago

  • Status changed from MODIFIED to CLOSED - CURRENTRELEASE

Please register to edit this issue

Also available in: Atom PDF