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.

Created attachment 1319344 [details]
log in production.log file

Description of problem: We were trying to list host collection for content host. But while trying to list host collection for content host, it didn't list host collection for that content host and production.log shows 500 Internal Server Error "NoMethodError: undefined method `order' for #<Array:0x00000012f95f58>" 


Version-Release number of selected component (if applicable): sat 6.3 snap 13


How reproducible: always


Steps to Reproduce:
1. Create content host
2. Add content host to host collection
3. Navigate to Host -> Content Host -> Host collections 

Actual results:
Results will not display host collection list and /var/log/foreman/production.log shows 500 internal server error.


Expected results:
list of host collections should be displayed.

Additional info:

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