Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 1043830

Summary: API lookup for unknown report ID fails with 500 error
Product: Red Hat Satellite Reporter: Tazim Kolhar <tkolhar>
Component: ProvisioningAssignee: jmagen <jmagen>
Status: CLOSED WORKSFORME QA Contact: Tazim Kolhar <tkolhar>
Severity: low Docs Contact:
Priority: unspecified    
Version: NightlyCC: asaleh, cwelton, dcleal, gkhachik, jmagen, omaciel, skottler
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: x86_64   
OS: Linux   
URL: http://projects.theforeman.org/issues/3894
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-05-26 17:42:49 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
foreman-debug none

Description Tazim Kolhar 2013-12-17 10:14:43 UTC
Created attachment 837623 [details]
foreman-debug

Description of problem:
Report command fails

Version-Release number of selected component (if applicable):
# rpm -qa | grep foreman
rubygem-hammer_cli_foreman-0.0.12-1.el6.noarch
foreman-compute-1.4.0-0.develop.201312131716git48a6510.el6.noarch
foreman-installer-1.4.0-0.develop.201312121158git282551d.el6.noarch
foreman-release-1.4.0-0.develop.201312131716git48a6510.el6.noarch
foreman-1.4.0-0.develop.201312131716git48a6510.el6.noarch
foreman-ovirt-1.4.0-0.develop.201312131716git48a6510.el6.noarch
foreman-proxy-1.4.0-0.develop.201312091021git42bab91.el6.noarch
foreman-postgresql-1.4.0-0.develop.201312131716git48a6510.el6.noarch
rubygem-foreman_api-0.1.8-1.el6.noarch
foreman-libvirt-1.4.0-0.develop.201312131716git48a6510.el6.noarch
foreman-selinux-1.4.0-0.develop.201311220906gite342a0b.el6.noarch


How reproducible:
everytime

Steps to Reproduce:
1.#  hammer report info --id 123
Error: 500 Internal Server Error

2.#  hammer report delete --id 123
Error: 500 Internal Server Error

3.# hammer report list 
No data.


Actual results:


Expected results:


Additional info:

Comment 1 RHEL Program Management 2013-12-17 10:25:20 UTC
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

Comment 2 Dominic Cleal 2013-12-17 10:26:29 UTC
Note that this only happens when the report ID is unknown, it should return a 404 error rather than 500.

Comment 5 jmagen@redhat.com 2014-05-22 07:59:16 UTC
can't reproduce. I get 404 error, not 500

Comment 6 Dominic Cleal 2014-05-22 08:12:26 UTC
Agreed, seems to work correctly now, returning a 404 for unknown report IDs.

Comment 7 Adam Saleh 2014-05-26 17:42:49 UTC
Returns 200 with {"message":"Could not evaluate: Could not retrieve information from environment production source(s) puppet://qetello02.usersys.redhat.com/plugins"}

Seems more reasonable than 500 with no explanation.