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 1482027[details]
screenshot of tasks while a puppet run happens
Description of problem:
When using tools like Puppet or Ansible to install packages, client systems to tend to execute many small yum transactions. Each transaction triggers a package profile update, which is quite expensive on the satellite.
Version-Release number of selected component (if applicable):
6.3.0
How reproducible:
100%
Steps to Reproduce:
1. for pkg in a b c; do yum install -y $pkg; done
Actual results:
3 package profile updates are created in Satellite
Expected results:
1 package profile update is created
Additional info:
maybe we can introduce some kind of a quiet period between the upload of a package list and the actual calculation. if a new upload happens in that period, the old one is thrown away and no calculation happens for it, only the newly uploaded data is considered.
As this came up in an IRC discussion earlier:
I think this should be implemented server-side.
A client-side solution would mean that the client needs either a daemon (can crash) or a cronjob (can be timed at a slot when the machine is not available/busy with other tasks) to upload the data later. So we might end up with unsubmitted data, which would confuse users.
Additionally, a client-side solution still allows users to submit more/frequently data than required, thus DoS-ing the server.
Comment 2sthirugn@redhat.com
2018-09-10 15:07:50 UTC
Great idea, we need to take care of a few things to implement on the server side:
If so many of these tasks get piled up (which is normal in large customers' patching cycles) this should not / have minimal impact on satellite performance (foreman-tasks, memory, etc) and this should not worry the system admins that thousands of profile package updates are pending.
Thank you for your interest in Satellite 6. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this, please do not reopen. Instead, feel free to contact Red Hat Technical Support. Thank you.
Created attachment 1482027 [details] screenshot of tasks while a puppet run happens Description of problem: When using tools like Puppet or Ansible to install packages, client systems to tend to execute many small yum transactions. Each transaction triggers a package profile update, which is quite expensive on the satellite. Version-Release number of selected component (if applicable): 6.3.0 How reproducible: 100% Steps to Reproduce: 1. for pkg in a b c; do yum install -y $pkg; done Actual results: 3 package profile updates are created in Satellite Expected results: 1 package profile update is created Additional info: maybe we can introduce some kind of a quiet period between the upload of a package list and the actual calculation. if a new upload happens in that period, the old one is thrown away and no calculation happens for it, only the newly uploaded data is considered.