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.

Bug 2260525

Summary: [Improvement] RefreshRepos step in Capsule Sync to refresh just repos to sync
Product: Red Hat Satellite Reporter: Odilon Sousa <osousa>
Component: Capsule - ContentAssignee: Pavel Moravec <pmoravec>
Status: CLOSED ERRATA QA Contact: Vladimír Sedmík <vsedmik>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.14.0CC: lblicha, momran, osousa, rlavi, sajha, smeyer, vsedmik
Target Milestone: 6.14.2Keywords: Performance, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: rubygem-katello-4.9.0.21-1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 2249913 Environment:
Last Closed: 2024-02-13 14:43:47 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Comment 2 Bryan Kearney 2024-01-26 16:03:01 UTC
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/36926 has been resolved.

Comment 4 Vladimír Sedmík 2024-01-29 17:47:24 UTC
Verified in 6.14.2 snap 2.0 with identical setup as https://bugzilla.redhat.com/show_bug.cgi?id=2249913#c5. Also, we will compare the results with the 6.14.2 snap 1.0 reproducer used there.

Steps to verify:
1. Have a Satellite with registered Capsule (unassigned LCE right now, caps autosync after promotion disabled).
2. Prepare the content to sync
  a) Sync several repos, I used these for example:
     ansible-2.9-for-rhel-8-x86_64-rpms                 
     rhel-7-server-ansible-2.9-rpms             
     rhel-7-server-kickstart                             
     rhel-7-server-rpms                                     
     rhel-8-for-x86_64-baseos-kickstart                   
     rhel-8-for-x86_64-baseos-rpms                                 
     rhel-9-for-x86_64-baseos-kickstart                   
     rhel-9-for-x86_64-baseos-rpms                                 
     rhel-6-server-els-satellite-client-6-rpms  
     rhel-7-server-satellite-client-6-rpms     
     satellite-client-6-for-rhel-8-x86_64-rpms         
     satellite-client-6-for-rhel-9-x86_64-rpms    
  b) Create 10 LCEs.
  c) Create 10 CVs, add all the repos, publish and promote to all LCEs from 2b).
3. Assign the Capsule with Library and all the LCEs from 2b).
4. Sync the Capsule.
5. Prepare one more CV with only one repo added (ansible-2.9-for-rhel-8-x86_64-rpms), publish and promote to all LCEs.
6. Sync the Capsule, check Dynflow and measure the sync time.
7. Add one more repo (rhel-6-server-els-satellite-client-6-rpms) to the CV, publish new version and promote it to all LCEs.
8. Sync the Capsule, check Dynflow and measure the sync time.
   
Results per points above:
6. Complete sync task took 22.3s (5.71s for RefreshRepos)
8. Complete sync task took 19.2s (6.00s for RefreshRepos)
Compared to the reproducer where the complete sync task took 353s (340s for RefreshRepos) we can mark this BZ as verified.

Comment 9 errata-xmlrpc 2024-02-13 14:43:47 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 (Important: Satellite 6.14.2 Async Security Update), 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-2024:0797