Bug 826133 - "503 Service unavailable" message when config server is down
"503 Service unavailable" message when config server is down
Status: NEW
Product: CloudForms Cloud Engine
Classification: Red Hat
Component: aeolus-conductor (Show other bugs)
1.0.0
Unspecified Unspecified
low Severity medium
: rc
: ---
Assigned To: Angus Thomas
Rehana
: Triaged
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-05-29 12:43 EDT by Jan Provaznik
Modified: 2013-01-29 10:57 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Jan Provaznik 2012-05-29 12:43:25 EDT
This bug was mentioned firstly here: https://bugzilla.redhat.com/show_bug.cgi?id=796528#c22 but since it's not related to the #796528 I'm putting it into separate BZ.

Steps to Reproduce:
1. stop aeolus-configserver service (but keep httpd running so proxy error is returned)
2. try to launch a deployable which uses configserver
3. you should get message "503 Service unavailable" - this message is not very descriptive
  
Expected results:
'Cannot connect to the config server' might be returned - this is returned if connection fails (apache is not running)

Additional info:
fix should be easy - we could extend app/models/instance.rb:add_instance_config! to catch 503 http code too, now it catches only connection errors:

    rescue Errno::ECONNREFUSED                                                  
      raise I18n.t 'deployments.errors.config_server_connection'                
    end

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