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.
DescriptionVladimír Sedmík
2024-01-19 09:24:10 UTC
Description of problem:
After Capsule sync the 'Update Content Counts' task is trigerred. In case of a bigger setup the task fails with error like:
PG::ProgramLimitExceeded: ERROR: index row requires 17440 bytes, maximum size is 8191
Version-Release number of selected component (if applicable):
6.15.0 snap 6.0
How reproducible:
always
Steps to Reproduce:
1. Have a Satellite with registered Capsule (unassigned LCE right now).
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.
Actual results:
After sync is done the Update Content Counts task is spawned and it fails with the PG::ProgramLimitExceeded error
Expected results:
The task should succeed without errors.
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.15.0 release), 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:2010
Description of problem: After Capsule sync the 'Update Content Counts' task is trigerred. In case of a bigger setup the task fails with error like: PG::ProgramLimitExceeded: ERROR: index row requires 17440 bytes, maximum size is 8191 Version-Release number of selected component (if applicable): 6.15.0 snap 6.0 How reproducible: always Steps to Reproduce: 1. Have a Satellite with registered Capsule (unassigned LCE right now). 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. Actual results: After sync is done the Update Content Counts task is spawned and it fails with the PG::ProgramLimitExceeded error Expected results: The task should succeed without errors.