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.
Runtime Error could not obtain pessimistic lock at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse when running multiple simultaneous registrations
DescriptionJoniel Pasqualetto
2024-03-08 15:30:03 UTC
Description of problem:
When running multiple systems registrations simultaneously, candlepin generates deadlocks on the database and returns the error from $subject
Version-Release number of selected component (if applicable):
How reproducible:
Always, on customer environment
Steps to Reproduce:
1. Force registration (or re-registration) of a large number of hosts (128 at the same time is what customer is doing)
Actual results:
Errors from $subject
Expected results:
Registration to work without errors
Additional info:
This appears to be the same issue reported on BZ 1758115, closed as WONTFIX.
Verified.
Version Tested: Satellite 6.14.4 Snap 2
Steps:
1. Force registration and re-registration on multiple hosts concurrently.
Observation:
No error observed in the logs while registration.
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 (Satellite 6.14.4 Async 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/RHBA-2024:2099