Project

Profile

Help

Issue #4627

closed

Pulp does not resync yum metadata files on change

Added by paji@redhat.com about 5 years ago. Updated almost 5 years ago.

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

Description

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 to RPM Support - Test #4824: Pulp does not resync yum metadata files on changeCLOSED - DUPLICATEActions
Copied to RPM Support - Issue #7030: Pulp does not resync yum metadata files on changeCLOSED - CURRENTRELEASEppickaActions
Actions #2

Updated by ttereshc about 5 years ago

  • Triaged changed from No to Yes
  • Sprint set to Sprint 51
Actions #3

Updated by bmbouter about 5 years ago

  • Tags Pulp 2 added
Actions #4

Updated by daviddavis almost 5 years ago

  • Sprint changed from Sprint 51 to Sprint 52
Actions #5

Updated by ttereshc almost 5 years ago

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

Added by ttereshc almost 5 years ago

Revision d9db7737 | View on GitHub

Perform sync even on metadata change only

Some metadata changes don't bump revision number, so a sync used to be no-op in such cases. Now checksum of repomd.xml is also taken into account.

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

Actions #6

Updated by ttereshc almost 5 years ago

  • Status changed from ASSIGNED to POST
Actions #7

Updated by dkliban@redhat.com almost 5 years ago

  • Platform Release set to 2.19.1
Actions #8

Updated by ttereshc almost 5 years ago

  • Status changed from POST to MODIFIED
Actions #9

Updated by dkliban@redhat.com almost 5 years ago

  • Sprint/Milestone set to 2.19.1
Actions #10

Updated by bherring almost 5 years ago

  • Copied to Test #4824: Pulp does not resync yum metadata files on change added

Added by ttereshc almost 5 years ago

Revision 2cb37ba8 | View on GitHub

Perform sync even on metadata change only

Some metadata changes don't bump revision number, so a sync used to be no-op in such cases. Now checksum of repomd.xml is also taken into account.

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

(cherry picked from commit d9db7737028ee8dc4df5af65bd3e1de8a67aae10)

Actions #11

Updated by ttereshc almost 5 years ago

Actions #12

Updated by dkliban@redhat.com almost 5 years ago

  • Status changed from MODIFIED to 5
Actions #13

Updated by dkliban@redhat.com almost 5 years ago

  • Status changed from 5 to CLOSED - CURRENTRELEASE
Actions #14

Updated by ttereshc almost 4 years ago

  • Copied to Issue #7030: Pulp does not resync yum metadata files on change added

Also available in: Atom PDF