Bug 785107

Summary: aeolus-configserver needs a human readable error instead of 404 resource not found
Product: [Retired] CloudForms Cloud Engine Reporter: Shveta <ssachdev>
Component: aeolus-conductorAssignee: Angus Thomas <athomas>
Status: CLOSED EOL QA Contact: Rehana <aeolus-qa-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 1.0.0CC: akarol, deltacloud-maint, hbrock
Target Milestone: rcKeywords: Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
404_error none

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