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 1479312 - Internal server error when viewing the activation-key host collections
Summary: Internal server error when viewing the activation-key host collections
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Activation Keys
Version: 6.3.0
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: Unspecified
Assignee: Brad Buckingham
QA Contact: Nikhil Kathole
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-08-08 10:52 UTC by Djebran Lezzoum
Modified: 2019-04-01 20:26 UTC (History)
2 users (show)

Fixed In Version: katello-3.4.5
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-02-21 16:54:37 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
host collection before add screen (70.33 KB, image/png)
2017-08-08 10:54 UTC, Djebran Lezzoum 		no flags Details
host collection when added screen (121.76 KB, image/png)
2017-08-08 10:54 UTC, Djebran Lezzoum 		no flags Details
host collection list added screen (94.15 KB, image/png)
2017-08-08 10:55 UTC, Djebran Lezzoum 		no flags Details
screenshot of UI listing host collection (51.80 KB, image/png)
2017-09-03 07:20 UTC, Nikhil Kathole 		no flags Details
log in production.log file (3.78 KB, text/plain)
2017-09-03 07:21 UTC, Nikhil Kathole 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 20580 0 Normal Closed "hammer host-collection list --host" produce error 500 - undefined method `order' 2020-03-19 12:57:12 UTC

Comment 1 Djebran Lezzoum 2017-08-08 10:54:00 UTC 
Created attachment 1310521 [details]
host collection before add screen
Comment 2 Djebran Lezzoum 2017-08-08 10:54:27 UTC 
Created attachment 1310522 [details]
host collection when added screen
Comment 3 Djebran Lezzoum 2017-08-08 10:55:19 UTC 
Created attachment 1310523 [details]
host collection list added screen
Comment 5 Brad Buckingham 2017-08-24 18:45:46 UTC 
The solution for this one is the same as bug 1479284.  Since the scenario is slightly different, I am going to link this bug to the same upstream redmine issue, so that it can also go through QE.
Comment 6 Nikhil Kathole 2017-09-03 07:18:32 UTC 
VERIFIED

Version Tested:
Satellite-6.3 Snap 14

steps:
1. Created host collection
2. Created activation key
3. navigate to activation key -> host collections -> add
4. Added host collection
5. Click on List/Remove

Successfully host collection is listed and production.log didn't show internal server error.
Comment 7 Nikhil Kathole 2017-09-03 07:20:02 UTC 
Created attachment 1321449 [details]
screenshot of UI listing host collection
Comment 8 Nikhil Kathole 2017-09-03 07:21:05 UTC 
Created attachment 1321450 [details]
log in production.log file
Comment 10 Satellite Program 2018-02-21 16:54:37 UTC 
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, 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-2018:0336
Note You need to log in before you can comment on or make changes to this bug.