Description of problem:
Issued filed here:
Prior to upgrading to pulp-2.8.7, syncing the same repo twice would only show the post sync actions (indexing, email, etc.) from occuring the first time.
After upgrading to pulp-2.8.7 it seems to always get kicked off. Upon further investigation this issue was discovered.
Version-Release number of selected component (if applicable):
pulp-2.8.7 (Satellite 6.2.3)
Steps to Reproduce:
1. Create a repo (ideally very large)
2. Sync the repo
3. Sync it again
On Satellite 6.2.3, step 3 is much much longer than on Satellite 6.2.2
I think i've narrowed down the reproducer steps:
1. On a satellite sync a repo with background download policy
2. Do one of the following:
run satellite-installer --reset
copy /var/lib/pulp/content to a new satellite install (in which case continue the rest of the steps on the new Satellite).
3. Create and Sync the same repository with background download policy
4. Create and sync the same repository AGAIN but with the immediate download policy
5. Sync the repo from step 4 again
Notice that post sync actions occured during step 5 and that pulp reports the update_count to be greater than 0.
I would argue this is NOT a blocker for 6.2.3
Is this a regression then?
The Pulp upstream bug status is at ASSIGNED. Updating the external tracker on this bug.
The Pulp upstream bug priority is at High. Updating the external tracker on this bug.
The Pulp upstream bug status is at POST. Updating the external tracker on this bug.
The Pulp upstream bug status is at MODIFIED. Updating the external tracker on this bug.
(In reply to Bryan Kearney from comment #4)
> Is this a regression then?
It is not a regression. This issue was introduced with new unit storage path calculation, which was changed before pulp 2.8
The Pulp upstream bug status is at ON_QA. Updating the external tracker on this bug.
The Pulp upstream bug status is at CLOSED - CURRENTRELEASE. Updating the external tracker on this bug.
All upstream Pulp bugs are at MODIFIED+. Moving this bug to POST.
Verified in Satellite 6.2.8 Snap 2.
I followed the steps outlined in #3 (copying to new satellite). The post_sync_skipped field was set to true for all post-sync actions. See attached image fore verification. I will also attach the output of relevant logs during the sync.
Created attachment 1250913 [details]
Created attachment 1250914 [details]
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.