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.
Tested on Satellite 6.3 Snap 18. Ran subscription of 50 cloned virtual machines in sequence.
# Before the registrations started:
$ grep "Request" /var/log/candlepin/candlepin.log | wc -l
1
# After the registration of 50 machines finished:
$ grep "Request" /var/log/candlepin/candlepin.log | wc -l
867
According to the initial report, more than 17 request per machine/subscription seems to be pretty excessive.
Comment 3Satellite Program
2017-10-16 10:08:37 UTC
Radovan, can you provide your candlepin.log so we can see exactly what was going on? This is strange as this was verified for 6.2.z and i don't see how it would have broken in 6.3.
(In reply to Justin Sherrill from comment #4)
> Radovan, can you provide your candlepin.log so we can see exactly what was
> going on? This is strange as this was verified for 6.2.z and i don't see
> how it would have broken in 6.3.
That Sat 6.3 instance is gone, unfortunately. I can try to reproduce the behaviour again, I still have the base client machine used as the clone-source and registration scripts. I will run the process overnight, and will let you know the result tomorrow.
Ok, I did tests you recommended in comment #8 and in BZ1431783 comment #11. Comparing number of Request calls for 50 hosts between 6.2 and 6.3, there was massive decrease for the "Subs attached => Subs removed" path (2020 less calls on 6.3), and less substantial, but still noticeable decrease for the "No subs attached => Subs attached" (465 less calls for 6.3).
Scenarios A and B from BZ1431783 comment #11 do pass as well.
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/RHSA-2018:0336