openstack team mailing list archive

[David Krider <david@xxxxxxxxxxxxxxx>]

I seem to be having this exact problem, but the fix doesn't work for me:

https://answers.launchpad.net/swift/+question/157858

No matter what I set the default_swift_cluster to, or if I add a bind_ip
to the DEFAULT section, I can't get X-Storage-Url to come back as
anything other than localhost:

dkrider@workstation:~$ curl -k -v -H 'X-Storage-User: test:tester' -H
'X-Storage-Pass: testing' https://<external_ip>:8080/auth/v1.0
* About to connect() to <external_ip> port 8080 (#0)
*   Trying <external_ip>... connected
* successfully set certificate verify locations:
*   CAfile: none
  CApath: /etc/ssl/certs
* SSLv3, TLS handshake, Client hello (1):
* SSLv3, TLS handshake, Server hello (2):
* SSLv3, TLS handshake, CERT (11):
* SSLv3, TLS handshake, Server finished (14):
* SSLv3, TLS handshake, Client key exchange (16):
* SSLv3, TLS change cipher, Client hello (1):
* SSLv3, TLS handshake, Finished (20):
* SSLv3, TLS change cipher, Client hello (1):
* SSLv3, TLS handshake, Finished (20):
* SSL connection using AES256-SHA
* Server certificate:
*      subject: C=AU; ST=Some-State; O=Internet Widgits Pty Ltd
*      start date: 2012-08-14 13:51:32 GMT
*      expire date: 2012-09-13 13:51:32 GMT
* SSL: unable to obtain common name from peer certificate
> GET /auth/v1.0 HTTP/1.1
> User-Agent: curl/7.22.0 (x86_64-pc-linux-gnu) libcurl/7.22.0
OpenSSL/1.0.1 zlib/1.2.3.4 libidn/1.23 librtmp/2.3
> Host: <external_ip>:8080
> Accept: */*
> X-Storage-User: test:tester
> X-Storage-Pass: testing
>
< HTTP/1.1 200 OK
< X-Storage-Url:
https://127.0.0.1:8080/v1/AUTH_e6ecde05-959a-4898-907b-5bec495fa4f0
< X-Storage-Token: AUTH_tk36c97915aed242b7b9a93aa05c06ba0c
< X-Auth-Token: AUTH_tk36c97915aed242b7b9a93aa05c06ba0c
< Content-Length: 113
< Date: Tue, 28 Aug 2012 18:38:34 GMT
<
* Connection #0 to host <external_ip> left intact
* Closing connection #0
* SSLv3, TLS alert, Client hello (1):
{"storage": {"default": "local", "local":
"https://127.0.0.1:8080/v1/AUTH_e6ecde05-959a-4898-907b-5bec495fa4f0"}}

Have I run into a bug, or is there something simple I'm overlooking in
the config file?

/etc/swift/proxy-server.conf
-----------------
[DEFAULT]
cert_file = /etc/swift/cert.crt
key_file = /etc/swift/cert.key
bind_port = 8080
workers = 8
user = swift

[pipeline:main]
pipeline = healthcheck cache swauth proxy-server

[filter:healthcheck]
use = egg:swift#healthcheck

[filter:cache]
use = egg:swift#memcache
memcache_servers = 10.1.7.10:11211,10.1.7.11:11211

[filter:swauth]
use = egg:swauth#swauth
set_log_level = DEBUG
super_admin_key = asdfqwer
default_swift_cluster =
local#https://<external_ip>:8080/v1#https://127.0.0.1:8080/v1

[app:proxy-server]
use = egg:swift#proxy
allow_account_management = true
account_autocreate = true
log_level = DEBUG