Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionJustin Sherrill
2016-10-10 13:40:55 UTC
Description of problem:
Issued filed here:
https://pulp.plan.io/issues/2328
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)
How reproducible:
Always
Steps to Reproduce:
1. Create a repo (ideally very large)
2. Sync the repo
3. Sync it again
Actual results:
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
OR
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
(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
Comment 10pulp-infra@redhat.com
2016-10-21 14:01:12 UTC
The Pulp upstream bug status is at ON_QA. Updating the external tracker on this bug.
Comment 11pulp-infra@redhat.com
2016-10-31 20:31:26 UTC
The Pulp upstream bug status is at CLOSED - CURRENTRELEASE. Updating the external tracker on this bug.
Comment 12pulp-infra@redhat.com
2016-11-21 21:00:40 UTC
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.
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.
https://access.redhat.com/errata/RHBA-2017:0447