Hi Tim, How are you? Thanks a lot for the quick response. I've change the cmd to point to the VIP of the KEYSTONE cluster and now I'm getting another error msg:
*# innobackupex ... | xbcloud put --storage=swift --swift-auth-url=http://VIP-KEYSTONE:8080/ <http://vip-swift-proxy:8080/> --swift-auth-version=3 --swift-user="dba:dba" --swift-password=xxxxxx --swift-container=BKP_TEST --verbose backup_full* * About to connect() to 10.xx.xx.xx port 8080 (#0) * Trying 10.xx.xx.xx... * connected * Connected to 10.xx.xx.xx (10.xx.xx.xx) port 8080 (#0) > POST /v3/auth/tokens HTTP/1.1 Host: 10.xx.xx.xx:8080 Content-Type: application/json Accept: application/json Content-Length: 139 * Closing connection #0 * Failure when receiving data from the peer error: curl_easy_perform() failed: Failure when receiving data from the peer error: failed to authenticate *German* 2016-07-12 11:13 GMT-03:00 Tim Burke <[email protected]>: > Hi German, > > It looks like you're using the Swift proxy server in your auth URL. Since > Keystone is handling user authentication, you'll want to use that server. > As part of the auth response, Keystone will provide a catalog of services > which should include Swift, and I expect your client will use that to > determine the storage URL. I'm not familiar with xbcloud, but if you have > configured Keystone to return multiple storage endpoints, you may need to > specify additional arguments to specify which region or interface to use. > > Tim > > On Jul 12, 2016, at 7:26 AM, German Anders <[email protected]> wrote: > > Hi all, > > I've a new Swift cluster with Mitaka release using Fernet tokens. > Everything works fine for now, but I want to try to backup some MySQL > databases using Percona xbcloud, and I'm having some issues there, has > anyone use this tool with Swift Mitaka? > > Basically I'm using the following syntax: > > *# innobackupex ... | xbcloud put --storage=swift > --swift-auth-url=http://VIP-SWIFT-PROXY:8080/ > <http://vip-swift-proxy:8080/> --swift-auth-version=3 > --swift-user="dba:dba" --swift-password=xxxxxx --swift-container=BKP_TEST > --verbose backup_full* > > * About to connect() to 10.x.x.x port 8080 (#0) > * Trying 10.x.x.x.... * connected > * Connected to 10.x.x.x (x.x.x.x) port 8080 (#0) > > POST /v3/auth/tokens HTTP/1.1 > Host: 10.x.x.x:8080 > Content-Type: application/json > Accept: application/json > Content-Length: 139 > > < HTTP/1.1 400 Bad Request > < Content-Length: 137 > < Content-Type: text/html; charset=UTF-8 > < X-Trans-Id: txe56xxxxxxxxxxxxx-xxxxxxxxxxx > < Date: Tue, 12 Jul 2016 12:12:54 GMT > < > * Connection #0 to host 10.x.x.x left intact > error: request failed with response code: 400 > * Closing connection #0 > error: failed to authenticate > > On the Proxy side I'm logging the following: > > Jul 12 08:12:29 swiftp01 proxy-server: Deferring reject downstream > Jul 12 08:12:29 swiftp01 proxy-server: - - 12/Jul/2016/12/12/29 HEAD > /v1/auth HTTP/1.0 204 - Swift - - - - tx718243dfedb14e7b9222f-005784dead - > 0.0174 RL - 1468325549.667370081 1468325549.684763908 - > Jul 12 08:12:29 swiftp01 proxy-server: Deferring reject downstream > Jul 12 08:12:29 swiftp01 proxy-server: 10.xx.xx.xx 10.xx.xx.xx > 12/Jul/2016/12/12/29 POST /v3/auth/tokens HTTP/1.0 400 - - - - 137 - > tx718243dfedb14e7b9222f-005784dead - 0.0232 - - 1468325549.664206028 > 1468325549.687386990 - > Jul 12 08:12:54 swiftp01 proxy-server: Deferring reject downstream > Jul 12 08:12:54 swiftp01 proxy-server: - - 12/Jul/2016/12/12/54 HEAD > /v1/auth HTTP/1.0 204 - Swift - - - - txe5614b378d454d0a81694-005784dec6 - > 0.0155 RL - 1468325574.074191093 1468325574.089672089 - > Jul 12 08:12:54 swiftp01 proxy-server: Deferring reject downstream > Jul 12 08:12:54 swiftp01 proxy-server: 10.xx.xx.xx 10.xx.xx.xx > 12/Jul/2016/12/12/54 POST /v3/auth/tokens HTTP/1.0 400 - - - - 137 - > txe5614b378d454d0a81694-005784dec6 - 0.0199 - - 1468325574.070952892 > 1468325574.090871096 - > > Any ideas? Could be that some parameter is missing? > > Thanks in advance, > > Best, > > *German* > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: [email protected]?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: [email protected]?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > >
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
