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.
Actions::Katello::Host::Update is one the most used actions in the foreman tasks/dynflow queue.
An example of a user who had 700,000 tasks in their task history saw this rough breakdown
COUNT|TYPE
320668 Actions::Katello::Host::Update
we need to investigate moving this to be handled directly by the main Rails application and not require the overhead of task creation, monitoring and eventual database cleanup.
So to test this
1. Register a host
2. ```subscription-manager facts --update```. This should trigger host update actions. May be you can change some fact like dmi.uuid mutiple times and run the same call and verify that the host facts were updated.
3. Updating the content view/release version for host as a host bulk action should also trigger this,
4. You can do Monitor -> Tasks and look for Actions::Katello::Host::Update and not find any since the time you triggered sub man facts update.
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-2020:1454