Sounds like you are experiencing a bug that was fixed in 3.5.1. You can work around this bug in older versions of pulp_rpm by setting optimize=False.
https://pulp.plan.io/issues/7228 On Mon, Aug 31, 2020 at 3:42 PM Bin Li (BLOOMBERG/ 120 PARK) < [email protected]> wrote: > Yes, we have 'mirror' = True. The remote repository has not changed. This > should not delete all packages from repo after sync. Version 2 repo in pulp > shows all packages are deleted while remote repo has not changed from > version 1. > > From: [email protected] At: 08/31/20 15:35:06 > To: Bin Li (BLOOMBERG/ 120 PARK ) <[email protected]> > Cc: [email protected] > Subject: Re: [Pulp-list] Pulp 3.3 sync issue from artifactory > > I suspect that you have 'mirror' = True in your 'sync' request[0]. With > this option set to True, the sync creates an exact copy of the remote > repository. If no packages are found, a new version is created without any > packages. When a subsequent sync occurs, no changes are detected, so a new > version is not created. > > [0] > https://pulp-rpm.readthedocs.io/en/latest/restapi.html#operation/repositories_rpm_rpm_sync > > On Mon, Aug 31, 2020 at 3:12 PM Bin Li (BLOOMBERG/ 120 PARK) < > [email protected]> wrote: > >> We created a rpm repos on artifactory and sync the repo to pulp 3.3. All >> packages are synced to pulp as version 1. If we run sync again, pulp could >> not find any packages and remove all previous packages in version 2. >> Subsequent sync also could not find any packages and the repo version stay >> as version 2. So far we only experience the issue when syncing from >> artifactory. Please advise. >> >> Thanks >> _______________________________________________ >> 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
