Bug 785107 - aeolus-configserver needs a human readable error instead of 404 resource not found
Summary: aeolus-configserver needs a human readable error instead of 404 resource not ...
Keywords:
Status: CLOSED EOL
Alias: None
Product: CloudForms Cloud Engine
Classification: Retired
Component: aeolus-conductor
Version: 1.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
Assignee: Angus Thomas
QA Contact: Rehana
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-27 10:26 UTC by Shveta
Modified: 2020-03-27 18:06 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:


Attachments (Terms of Use)
404_error (205.17 KB, image/png)
2012-01-27 10:26 UTC, Shveta
no flags Details

Description Shveta 2012-01-27 10:26:18 UTC
Created attachment 557837 [details]
404_error

Description of problem:


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Trying to add a non-existent or invalid configerver shows 404 , Resource not found error. 
2. 
3.
  
Actual results:


Expected results:


Additional info:

rpm -qa|grep aeolus
aeolus-configserver-0.4.5-2.el6.noarch

Comment 1 Greg Blomquist 2012-02-01 18:41:13 UTC
Changing the version to 1.0 (found in 1.0)

Adding the cloudforms-1.1? flag (to reflect what version originally said)

Comment 2 Greg Blomquist 2012-05-04 17:39:58 UTC
This is something to be fixed in the conductor web UI


Note You need to log in before you can comment on or make changes to this bug.