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.
Comment 5Lukáš Hellebrandt
2020-07-28 12:39:00 UTC
Verified with Sat 6.7.2 snap 2.0.
This is hard to verify as there is no real reproducer nor is it concretely specified how this bug actually manifests. I had a Satellite, an external Capsule and a Host registered through that Capsule. I tried to cause huge sync load on both Satellite and Capsule. During this time, I tried to also run different tasks on the hosts, e.g. ran a command through remote execution. I measured systems load which was high due to ~25 repos being synced at a time but nothing was unusually or unexpectably slow. Most CPU time was taken by pulp workers which is expected when syncing. I haven't noticed any files growing too much (cache grew a few GBs and shrinked after the operation) or lowered responsibility at any time. The remote commands have been ran correctly and almost immediately. Dynflow log looks ok. To conclude, I haven't noticed any issues while doing a large Capsule 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-2020:3255