Bug 497528 - Improper error message from some systemgroup API calls
Summary: Improper error message from some systemgroup API calls
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Network
Classification: Retired
Component: RHN/API
Version: RHN Devel
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Sebastian Skracic
QA Contact: Red Hat Network Quality Assurance
URL:
Whiteboard: us=86777
Depends On:
Blocks: rhn-sprint22
TreeView+ depends on / blocked
 
Reported: 2009-04-24 13:44 UTC by Stephen Herr
Modified: 2009-05-01 19:05 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-04-29 19:27:22 UTC
Embargoed:

Attachments (Terms of Use)

Description Stephen Herr 2009-04-24 13:44:06 UTC 
Description of problem:
When given a group that does not exist most systemgroup API calls throw an error that indicates as much. However, getDetails, listActiveSystemsInGroup, and listInactiveSystemsInGroup do not, they throw errors with "Message not found." as the message. This should be fixed.
  
Actual results:
"Message not found." error.

Expected results:
"unhandled internal exception: Unable to locate or access server group: <group>" error.
Comment 1 Sebastian Skracic 2009-04-24 17:25:21 UTC 
Pushed in 2f837a94b605569d5a650cfd7ddd8e6dc7ba65d0.
Comment 2 Stephen Herr 2009-04-29 19:27:22 UTC 
verified
Note You need to log in before you can comment on or make changes to this bug.