-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open Stack - 503 Service Unavailable #3696
Comments
Hi, Have you try to place your debug code into this function: https://github.com/fog/fog/blob/master/lib/fog/openstack/storage.rb#L144 btw, i think 503 error that relate to server thing. |
I have used httplog to watch requests. I did find an issue. When adding the :query => {'format' => 'json'} to requests (this is in the ruby files in the requests folder), this literally adds {'format' => 'json'} to the query string. The :query option is looking for a string literal such as '?format=json' I have still not figured out the problem. The Open Stack command line tools work so the server is there and working fine. I will look at it further tomorrow. |
I haven't gotten any closer to solving this. I wrote a small Ruby script using Net:HTTP to talk to the OpenStack api and it works fine. The command line tools work fine. There is something wrong in fog with OpenStack. Maybe it is an api version thing or something? Any pointers on where to look within fog to solve this? |
It works fine for me:
You could try to compare 2 http requests, one comes from CLI tool, one comes from Fog, to find different things between them, i think :) |
Closing in favor of fog/fog-openstack#50 |
Hi there,
I am trying to get fog working with swift at an OpenStack provider. I get what seems to be a correct service object after creation (correct urls and credentials for interacting with swift). When I try to use that object, I get 503 Service Unavailable for requests. How can I debug this? I get the full excon response object after the unexpected response. Am I able to capture the request object so that I can see what is going on?
Thanks,
Robert
The text was updated successfully, but these errors were encountered: