Bug 746650 - AJAX error responses are not displayed
Summary: AJAX error responses are not displayed
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: 2011-10-17 11:56 UTC by Jan Provaznik
Modified: 2020-03-27 19:42 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-27 19:42:44 UTC
Embargoed:

Attachments (Terms of Use)
proxy_err (209.28 KB, image/png)
2012-02-15 10:45 UTC, Shveta 		no flags Details
httpd stop (197.53 KB, image/png)
2012-02-24 08:00 UTC, Shveta 		no flags Details
View All

Description Jan Provaznik 2011-10-17 11:56:43 UTC 
Description of problem:
We don't display any error when ajax request fails, this happens for example when loading any tab.

Steps to Reproduce:
1. Go to a pool show page
2. Stop conductor
3. Click on the "Deployments" tab
  
Actual results:
Loading icon is shown foreever

Expected results:
Display an error message.

Additional info:
Comment 2 wes hayutin 2012-01-03 17:42:39 UTC 
adding ce-sprint-next bugs to ce-sprint
Comment 3 wes hayutin 2012-01-24 18:04:08 UTC 
lets try to recreate
Comment 5 Shveta 2012-02-15 10:45:24 UTC 
Monitor --pretty view 
Stopped conductor
Clicked on application


This is what i got :
Proxy Error
The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request GET /conductor/pools.
Reason: Error reading from remote server
Apache/2.2.15 (Red Hat) Server at qe-blade-10.idm.lab.bos.redhat.com Port 443
Comment 6 Shveta 2012-02-15 10:45:53 UTC 
Created attachment 562184 [details]
proxy_err
Comment 7 Shveta 2012-02-24 08:00:02 UTC 
Created attachment 565521 [details]
httpd stop

Service httpd stop and click on application , blank page is launched.
rpm -qa|grep aeolus
aeolus-conductor-0.8.0-35.el6.noarch
rubygem-aeolus-cli-0.3.0-10.el6.noarch
aeolus-conductor-doc-0.8.0-35.el6.noarch
rubygem-aeolus-image-0.3.0-9.el6.noarch
aeolus-all-0.8.0-35.el6.noarch
aeolus-conductor-daemons-0.8.0-35.el6.noarch
aeolus-configure-2.5.0-15.el6.noarch
Comment 8 Hugh Brock 2012-02-24 15:17:35 UTC 
Not clear that this is a real bug, but if it is it's certainly not a 1.0.0 bug.
Note You need to log in before you can comment on or make changes to this bug.