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.

Request:

<pre>
{
	"included": {
		"ids": [],
		"resources": [],
		"params": {
			"organization_id": "1",
			"paged": true,
			"page": 1,
			"per_page": "20",
			"search": "name= awesome-client.sat-r220-10.example.com"
		}
	},
	"excluded": {
		"ids": []
	},
	"errata_ids": ["RHEA-2012:0055"],
	"organization_id": "1"
}
</pre>

Response:

<pre>
{
	"displayMessage": "No hosts have been specified.",
	"errors": ["No hosts have been specified."]
}
</pre>

Steps to Reproduce:

# Go to errata page
# Select on or more errata and click apply
# Select all content hosts using the checkbox and then click "select all ___" (requires https://github.com/Katello/katello/pull/7086)
# Click next
# Note above error

Created from redmine issue http://projects.theforeman.org/issues/21897

Upstream bug assigned to jsherril

Actually this is working fine as designed

*** Bug 1532385 has been marked as a duplicate of this bug. ***