Bug 1976213
Summary: | Search filter on report causes task to crash, and sometimes OOM error | ||
---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Gary Scarborough <gscarbor> |
Component: | Reporting | Assignee: | Partha Aji <paji> |
Status: | CLOSED ERRATA | QA Contact: | Satellite QE Team <sat-qe-bz-list> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 6.9.0 | CC: | casl, ikaur, jlenz, lvrtelov, mhulan, paji, pmendezh, rlavi, zhunting |
Target Milestone: | 6.15.0 | Keywords: | Performance, Triaged |
Target Release: | Unused | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | rubygem-katello-4.11.0.3-1 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2024-04-23 17:10:46 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Gary Scarborough
2021-06-25 14:25:13 UTC
Just updating as the Satellite version is 6.9.1 Is the issue related to searching by "installed_package_name" only? This search term may need to get optimized. Or are there other search terms that cause problems? I can't answer regarding other search terms, as this was my specific need. The search itself is something that should not be so resource intensive as to cause OOM. I understand the "runaway query" scenario, but this was very simple. RH support provided this SQL which has no noticible performance impact: ... select h.name,kip.name,kip.nvra from hosts as h, katello_host_installed_packages as khip, katello_installed_packages as kip where kip.id=khip.installed_package_id and khip.host_id=h.id and kip.name like '$1' ... Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team. Thank you. This issue persists on 6.13.2 There does not seem to be much interest in the satellite reporting features. I will mention as I have in other BZs, that features such as this, if they are not to be usable in any practical sense, should be removed from future releases. Charles, I appreciate your feedback and interest in Satellite's reporting. I am going to update the bugzilla so that it doesn't go through auto-closure so that additional investigation can be performed. There was a private comment where an engineer was looking to confirm if this persisted on 6.13 and I appreciate your feedback that it does. To your point regarding 'interest in the satellite reporting features', the Reporting feature has had over 150 bugzillas resolved since it was introduced, including over 50 enhancement requests. While it is unfortunate that this issue does exist, the data does indicate that there is interest and activity in this area. Thank you for your understanding. Upstream bug assigned to paji Upstream bug assigned to paji Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/35974 has been resolved. 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 (Important: Satellite 6.15.0 release), 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-2024:2010 |