Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 643989

Summary: [UI]: Entering a new provider account always leaves me at a Proxy Error
Product: [Retired] CloudForms Cloud Engine Reporter: Chris Lalancette <clalance>
Component: aeolus-conductorAssignee: Scott Seago <sseago>
Status: CLOSED CURRENTRELEASE QA Contact: wes hayutin <whayutin>
Severity: medium Docs Contact:
Priority: low    
Version: 0.3.1CC: dajohnso, deltacloud-maint
Target Milestone: alpha   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-06-14 15:48:11 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 651514    

Description Chris Lalancette 2010-10-18 18:04:51 UTC 
Description of problem:
With the latest qe-drop2, entering a new Provider Account leaves me at an error page.

Steps to Reproduce:
1.  Start from a completely fresh deltacloud build (# deltacloud-cleanup; deltacloud-configure)
2.  Login to the UI with admin/password
3.  System Settings -> Manage Providers -> New Provider
4.  Enter in details for EC2 (in the beta, this is http://localhost:3002/api)
5.  Click on "Provider Account".
6.  Add in all of the information for the provider account
7.  Click on "Add"
  
Actual results:
Account is properly inserted into the database.  Error page is shown:

Proxy Error

The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request GET /deltacloud/provider/accounts/1.

Reason: Error reading from remote server

Apache/2.2.16 (Fedora) Server at virtlab6.virt.bos.redhat.com Port 80

Expected results:
Account is properly inserted into database.  No error page is shown.
Comment 1 wes hayutin 2011-06-14 15:48:11 UTC 

*** This bug has been marked as a duplicate of bug 651562 ***
Comment 2 wes hayutin 2011-12-08 14:07:11 UTC 
perm close