[Pulp-list] pulp3 repository version keep increasing

Dennis Kliban dkliban at redhat.com
Mon Nov 4 16:11:36 UTC 2019


On Mon, Nov 4, 2019 at 10:08 AM Bin Li (BLOOMBERG/ 120 PARK) <
bli111 at bloomberg.net> wrote:

> We are planning to sync all repos everyday and would prefer the version
> doesn't increment if repo content are the same. Just wondering how we can
> compare the remote content with pulp repo content so we run sync only if
> the remote content is changed?
>
>
The only way to know if the content changed in the remote repository is to
check the metadata. This is what Pulp does during a sync. We decided to
always increment the repository version so that it will be clear to the
user that Pulp performed a sync operation. The user can then examine the
repository version and see what content was added or removed. If nothing
was added or removed, then nothing changed in the remote repository. Does
that kind of check work for you? How does this affect your workflow?


> Thanks
> From: daviddavis at redhat.com At: 10/24/19 05:47:56
> To: Bin Li (BLOOMBERG/ 120 PARK ) <bli111 at bloomberg.net>
> Cc: pulp-list at redhat.com
> Subject: Re: [Pulp-list] pulp3 repository version keep increasing
>
> This is an expected behavior. See https://pulp.plan.io/issues/3308. Feel
> free to comment with any thoughts you have.
>
> David
>
>
> On Wed, Oct 23, 2019 at 8:58 PM Bin Li (BLOOMBERG/ 120 PARK) <
> bli111 at bloomberg.net> wrote:
>
>> Any idea why repository version keep increasing even nothing was updated
>> in the repo? I synced the repo from the same remote repo which always has
>> the same content. The repo version increment every times I run sync. Below
>> is output from version href. It shows nothing was added to repo and the
>> total number of packages is the same.
>>
>>
>>
>>
>> "results": [
>> {
>> "base_version": null,
>> "content_summary": {
>> "added": {},
>> "present": {
>> "rpm.package": {
>> "count": 819,
>> "href":
>> "/pulp/api/v3/content/rpm/packages/?repository_version=/pulp/api/v3/repositories/7f1bc351-a1bd-4bf7-b7ee-0fc9fca592c7/versions/4/"
>> }
>> },
>> "removed": {}
>> },
>> "number": 4,
>> "pulp_created": "2019-10-23T18:16:31.331868Z",
>> "pulp_href":
>> "/pulp/api/v3/repositories/7f1bc351-a1bd-4bf7-b7ee-0fc9fca592c7/versions/4/"
>> },
>> {
>> "base_version": null,
>> "content_summary": {
>> "added": {},
>> "present": {
>> "rpm.package": {
>> "count": 819,
>> "href":
>> "/pulp/api/v3/content/rpm/packages/?repository_version=/pulp/api/v3/repositories/7f1bc351-a1bd-4bf7-b7ee-0fc9fca592c7/versions/3/"
>> }
>> },
>> "removed": {}
>> },
>> "number": 3,
>> "pulp_created": "2019-10-23T18:15:24.285845Z",
>> "pulp_href":
>> "/pulp/api/v3/repositories/7f1bc351-a1bd-4bf7-b7ee-0fc9fca592c7/versions/3/"
>> },
>>
>>
>> Thanks
>> _______________________________________________
>> Pulp-list mailing list
>> Pulp-list at redhat.com
>> https://www.redhat.com/mailman/listinfo/pulp-list
>
>
> _______________________________________________
> Pulp-list mailing list
> Pulp-list at redhat.com
> https://www.redhat.com/mailman/listinfo/pulp-list
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/pulp-list/attachments/20191104/6ca75d9c/attachment.htm>


More information about the Pulp-list mailing list