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.
Bug 1579214 - hammer host list takes a long time
Summary: hammer host list takes a long time
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Hosts
Version: 6.3.1
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: tstrych
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-05-17 07:44 UTC by Michal Dekan
Modified: 2023-03-24 14:05 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-01-15 20:29:57 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1447958 0 urgent CLOSED [regression] host search by organization never finishes but causes mem.leak in foreman process 2021-08-30 12:18:58 UTC

Internal Links: 1447958

Description Michal Dekan 2018-05-17 07:44:37 UTC 
Description of problem:

It takes ~20 seconds to display 229 hosts with hammer on the box which is powerful enough to definitely has a better time (24 CPUs, 50GB RAM).

Version-Release number of selected component (if applicable):

satellite-6.3.1-3.el7sat.noarch

How reproducible:


Steps to Reproduce:

Satellite 6.3.1 running on the similar box like mentioned above with 229 hosts attached to it.

Actual results:

[root@gprfc018 ~]# time hammer -u admin -p XXXX host list
----|-------------------------------------|------------------|------------|--------------|-------------------|---------------------------|----------------------
ID  | NAME                                | OPERATING SYSTEM | HOST GROUP | IP           | MAC               | CONTENT VIEW              | LIFECYCLE ENVIRONMENT
----|-------------------------------------|------------------|------------|--------------|-------------------|---------------------------|----------------------
1   | gprfc018.sbu.lab.eng.bos.redhat.com | RedHat 7.5       |            | 10.16.154.51 | d4:be:d9:b3:90:2b |                           |                      [...]
89  | gprfc027container78.example.com     | RedHat 7.4       | HostGroup  | 172.27.0.78  | 02:42:ac:1b:00:4e | Default Organization View | Library              ----|-------------------------------------|------------------|------------|--------------|-------------------|---------------------------|----------------------

real    0m21.635s
user    0m2.309s
sys     0m0.221s

Expected results:

Should be faster, there was a customer complain about slow hammer host list (case attached) in satellite 6.2.11. This test reveals that its not much better in current 6.3 (6.3.1)

Additional info:
Comment 12 Bryan Kearney 2019-12-03 16:34:26 UTC 
The Satellite Team is attempting to provide an accurate backlog of bugzilla requests which we feel will be resolved in the next few releases. We do not believe this bugzilla will meet that criteria, and have plans to close it out in 1 month. This is not a reflection on the validity of the request, but a reflection of the many priorities for the product. If you have any concerns about this, feel free to contact Red Hat Technical Support or your account team. If we do not hear from you, we will close this bug out. Thank you.
Comment 13 Bryan Kearney 2020-01-15 20:29:57 UTC 
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.
Comment 14 Bryan Kearney 2020-01-15 20:30:07 UTC 
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.
Note You need to log in before you can comment on or make changes to this bug.