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.
Created attachment 1414121[details]
[Verification] Screenshot1 Attached - passenger-requests processed in few seconds
Verified!
@ Satellite 6.3.1 snap 1.0
Steps:
---------------
1. Set up a new satellite and configure it to have 24 passenger workers(That is 1.5 of 16 CPU cores on satellite as per document - https://access.redhat.com/documentation/en-us/red_hat_satellite/6.2/html/installation_guide/large_deployment_considerations).
2. Set up 15 clients to register to the Satellite in a loop, using subscription-manager register --force with an activation key.
3. on the satellite,
# watch "passenger-status --show=requests | grep -e 'uri\|connected'".
Behavior:
---------------
is: Expected
Detail:
1. The satellite in processing registration requests in very few seconds. Maximum 3 seconds.
2. There were no pending passenger requests for long time and every passenger request is processed and done.
Attaching foreman-passenger requests screenshot.
As per comment 8, The steps and behavior both are correct and expected. Hence changing the bug status to Verified!
The comment 7 issue is out of scope of this bug.
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-2018:1126