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.
Steps to retest:
1. Configure a Satellite with 60K entitled Candlepin consumers.
2. Double the default values for Tomcat's Java heap memory minimum and maximum:
# grep JAVA_OPTS /etc/tomcat/tomcat.conf
JAVA_OPTS="-Xms2048m -Xmx8192m"
3. Refresh the manifest:
# time hammer subscription refresh-manifest --organization-id 1
[.................................................] [100%]
real 39m6.116s │
user 0m9.633s │
sys 0m1.498s
4. Delete the manifest:
# time hammer subscription delete-manifest --organization-id 1
[.................................................] [100%]
real 0m10.218s
user 0m1.659s
sys 0m0.251s
5. Import a manifest:
# time hammer subscription upload --file manifest_1919417_20210211T160313Z.zip --organization-id 1
warning: Overriding "Content-Type" header "multipart/form-data" with "multipart/form-data; boundary=----RubyFormBoundaryOvdKUh5RbWUDpBGk" due to payload
[.............................................................................................................] [100%]
real 0m9.427s
user 0m1.737s
sys 0m0.206s
Expected Results:
On a Satellite with 60K or more Candlepin consumers, refreshing, deleting, and importing a manifest should all complete successfully in a timely fashion.
Actual Results:
Manifest refresh completes in under 40 minutes (vs. encountering "Error: Runtime Error This connection has been closed. at org.postgresql.jdbc.PgConnection.checkClosed:767" on Satellite 6.8.2). Manifest delete and import complete in approximately ten seconds each.
Verified on Satellite 6.8.4, snap 1 (candlepin 3.1.24-1).
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.8.4 Async Bug Fix 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-2021:0654
Steps to retest: 1. Configure a Satellite with 60K entitled Candlepin consumers. 2. Double the default values for Tomcat's Java heap memory minimum and maximum: # grep JAVA_OPTS /etc/tomcat/tomcat.conf JAVA_OPTS="-Xms2048m -Xmx8192m" 3. Refresh the manifest: # time hammer subscription refresh-manifest --organization-id 1 [.................................................] [100%] real 39m6.116s │ user 0m9.633s │ sys 0m1.498s 4. Delete the manifest: # time hammer subscription delete-manifest --organization-id 1 [.................................................] [100%] real 0m10.218s user 0m1.659s sys 0m0.251s 5. Import a manifest: # time hammer subscription upload --file manifest_1919417_20210211T160313Z.zip --organization-id 1 warning: Overriding "Content-Type" header "multipart/form-data" with "multipart/form-data; boundary=----RubyFormBoundaryOvdKUh5RbWUDpBGk" due to payload [.............................................................................................................] [100%] real 0m9.427s user 0m1.737s sys 0m0.206s Expected Results: On a Satellite with 60K or more Candlepin consumers, refreshing, deleting, and importing a manifest should all complete successfully in a timely fashion. Actual Results: Manifest refresh completes in under 40 minutes (vs. encountering "Error: Runtime Error This connection has been closed. at org.postgresql.jdbc.PgConnection.checkClosed:767" on Satellite 6.8.2). Manifest delete and import complete in approximately ten seconds each. Verified on Satellite 6.8.4, snap 1 (candlepin 3.1.24-1).