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.
DescriptionJulio Entrena Perez
2017-04-13 12:47:57 UTC
Created attachment 1271429[details]
dynflow console for capsule sync task
Description of problem:
This is the continuation of bug 1388296 for Puppet content.
Bug 1388296 addresses the problem for RPM content, this bug is for the same issue with Puppet content.
Version-Release number of selected component (if applicable):
tfm-rubygem-katello-3.0.0.105-2.BZ1388296.el7sat (Satellite 6.2.8 + hotfix from https://bugzilla.redhat.com/show_bug.cgi?id=1388296#c50 with the fix for bug 1388296).
How reproducible:
Always
Steps to Reproduce:
1. Run a Capsule sync when all repositories are already in sync.
2.
3.
Actual results:
All RPM repositories sync in a short amount of time.
Puppet repositories take much longer (more than 5,000 seconds).
Expected results:
Puppet repositories that are already in sync don't take large amounts of time to synchronise to the Capsules.
Additional info:
Check step 216 in attached dynflow console html page for a Capsule sync task.
All repos complete quickly but the Puppet repo in step 216 that, despite being already in sync, still took 5264 seconds.
Verified!
@ Satellite 6.3 snap 30
Steps:
Re-run a Capsule sync when all repositories including puppet are already in sync.
Environment:
1. The capsule was set to On_Demand mode.
2. Tested in both capsule sync modes 'optimized sync' and 'complete sync'.
3. The test was conducted on 'OpenStack' puppet module.
Observation:
1. Puppet repositories which are already in sync didn't take a large time to sync. They were very quick.
2. I also see this in sync dynflow logs(complete capsule sync mode only):
id: 5a55f9e9f42bed8334f9ea52
details: 'Skipped: Repository content has not changed since last publish.'
3. In optimized sync mode, 'puppet repo' sync took just 2.37 seconds.
4. In Complete sync mode, 'puppet repo' sync took just 2.50 seconds
Screenshots are attached.
Please feel free to reopen if steps, environment or the observation is incorrect.
Comment 21Satellite Program
2018-02-21 16:54:37 UTC
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/RHSA-2018:0336