This issue might have been fixed in 3.8 https://pulp.plan.io/issues/7030
-------- Regards, Ina Panova Senior Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go instead where there is no path and leave a trail." On Thu, Jan 14, 2021 at 3:33 PM Dennis Kliban <[email protected]> wrote: > We have historically treated the revision number as required. Please file > an issue at https://pulp.plan.io/issues/new/ and we will investigate what > the behavior should be in this situation. > > On Wed, Jan 13, 2021 at 6:06 PM Bin Li (BLOOMBERG/ 120 PARK) < > [email protected]> wrote: > >> I noticed the repomd.xml on artifactory is a little different (see >> below). This is why pulp doesn't sync when optimize is true. Is the >> revision optional field in repomd.xml? >> >> <?xml version="1.0"?> >> <repomd xmlns="http://linux.duke.edu/metadata/repo"; xmlns:rpm=" >> http://linux.duke.edu/metadata/rpm";> >> <data type="other"> >> <location >> href="repodata/deddaac9159b0dd137637e3f054699ed835c2188-other.xml.gz"/> >> <checksum type="sha" >> pkgid="YES">deddaac9159b0dd137637e3f054699ed835c2188</checksum> >> <size>55565</size> >> <timestamp>1610569598</timestamp> >> <open-checksum type="sha" >> pkgid="YES">440b3887bd333a9f198daf8d11d883c39b9cfa6b</open-checksum> >> <open-size>163364</open-size> >> <revision/> >> </data> >> <data type="filelists"> >> <location >> href="repodata/2ab424ed2e5cb27ded110002678a64efe61fdc6c-filelists.xml.gz"/> >> <checksum type="sha" >> pkgid="YES">2ab424ed2e5cb27ded110002678a64efe61fdc6c</checksum> >> <size>722</size> >> <timestamp>1610569598</timestamp> >> <open-checksum type="sha" >> pkgid="YES">7b21b424589b3d0fcbfb5e78b5eb21441a739dd5</open-checksum> >> <open-size>3064</open-size> >> <revision/> >> </data> >> <data type="primary"> >> <location >> href="repodata/18af240dc9319adc1fc746da197f195d35d3fca6-primary.xml.gz"/> >> <checksum type="sha" >> pkgid="YES">18af240dc9319adc1fc746da197f195d35d3fca6</checksum> >> <size>1724</size> >> <timestamp>1610569599</timestamp> >> <open-checksum type="sha" >> pkgid="YES">49ad32d347e2bde51dd070085cbe145b0146faf4</open-checksum> >> <open-size>9708</open-size> >> <revision/> >> </data> >> >> >> From: [email protected] At: 01/13/21 14:36:27 >> To: Bin Li (BLOOMBERG/ 120 PARK ) <[email protected]> >> Cc: [email protected] >> Subject: Re: [Pulp-list] mirrored sync in 3.7.3 >> >> The sync task examines the repomd.xml and the revision number in it. All >> the logic for optimizing the sync is here[0]. >> >> [0] >> https://github.com/pulp/pulp_rpm/blob/3.7/pulp_rpm/app/tasks/synchronizing.py#L169-L175 >> >> On Wed, Jan 13, 2021 at 1:45 PM Bin Li (BLOOMBERG/ 120 PARK) < >> [email protected]> wrote: >> >>> Happy new year. >>> I run a mirrored sync with upstream. The sync didn't pick up new rpms in >>> upstream repo. I rerun sync with optimize=false and it synced all rpms. I >>> do see the file names from new rpms are in the filelists.xml.gz of the >>> upstream repodata. Just wondering which repo data does pulp check before >>> starting a optimized mirror sync and why the optimized sync didn't work? >>> _______________________________________________ >>> Pulp-list mailing list >>> [email protected] >>> https://www.redhat.com/mailman/listinfo/pulp-list >> >> >> _______________________________________________ > Pulp-list mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/pulp-list
_______________________________________________ Pulp-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/pulp-list
