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.

Description of problem:

Customer wants only a simple list of hosts.

The default action apparently calculates all installable errata counts for every host and takes way too long when I simply want a list of content hosts.  

Additionally, why try to calculate errata on ESX hypervisors?  there will never be any.  Also, can a filter be added to exclude hypervisors from the list?


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

6.1.5

How reproducible:

Repeatably

Steps to Reproduce:
1.run # hammer content-host list and observe database and system activity


Actual results:

The command takes over four minutes to run.


Expected results:

Comes back with a simple list of content hosts.


Additional info:

Perhaps a flag could be added to allow just a simple list of hosts.

Marking this as a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1461194 which will be delivered in 6.2.12. This will address the performance concerns.

*** This bug has been marked as a duplicate of bug 1461194 ***