Comment 1 for bug 954086

is it possible this is a load-balancer issue? I've tried to duplicate this, but cannot. I wrapped all my services in ssl using socat, and updated my service catalog to show only ssl endpoints, and wasn't able to replicate it.

stack@devstack:~/devstack$ nova --insecure --debug volume-list
connect: (127.0.0.1, 15000)
send: 'POST /v2.0/tokens HTTP/1.1\r\nHost: 127.0.0.1:15000\r\nContent-Length: 100\r\ncontent-type: application/json\r\naccept-encoding: gzip, deflate\r\naccept: application/json\r\nuser-agent: python-novaclient\r\n\r\n{"auth": {"tenantName": "demo", "passwordCredentials": {"username": "admin", "password": "secret"}}}'
reply: 'HTTP/1.1 200 OK\r\n'
header: Content-Type: application/json
header: Vary: X-Auth-Token
header: Content-Length: 2172
header: Date: Thu, 15 Mar 2012 01:40:50 GMT
connect: (192.168.122.118, 18776)
send: u'GET /v1/36d50c9cf2bb4fd2bdf098b683094aa3/volumes/detail HTTP/1.1\r\nHost: 192.168.122.118:18776\r\nx-auth-project-id: demo\r\nx-auth-token: f0f13233e58a4fb1ad4d886e7a46be77\r\naccept-encoding: gzip, deflate\r\naccept: application/json\r\nuser-agent: python-novaclient\r\n\r\n'
reply: 'HTTP/1.1 200 OK\r\n'
header: X-Compute-Request-Id: req-a936f2ca-4943-4292-b9e6-6c878a70d0ea
header: Content-Type: application/json
header: Content-Length: 486
header: Date: Thu, 15 Mar 2012 01:40:50 GMT
+----+-----------+--------------+------+-------------+-------------+
| ID | Status | Display Name | Size | Volume Type | Attached to |
+----+-----------+--------------+------+-------------+-------------+
| 1 | error | foo | 10 | None | |
| 2 | available | foo | 1 | None | |
+----+-----------+--------------+------+-------------+-------------+

is the 503 from the load balancer, or the volume service? do you have nova-volume logs you can show from the same request?

I'd like to be able to reproduce this.