PDA

View Full Version : amanda 3.4.3 and Swift keystone



kladiv
March 24th, 2017, 07:19 AM
Hello,
does S3 Device support Swift using Keystone authentication? (like OVH Object Storage) ?
I did some tests but authentication seems not work.

Thank you

Best,
Claudio

paddy
March 24th, 2017, 08:44 AM
What version of Swift are you using? We have tested with Icehouse and Juno (not with recent releases) with keystone auth.

kladiv
March 24th, 2017, 08:52 AM
Hi, i'm trying with OVH Object Storage.
Can you help me? Maybe i miss some S3 Device configurations?

Here some OVH useful links:
https://www.ovh.com/us/public-cloud/storage/object-storage/
https://www.ovh.com/us/g1921.creating_object_container
https://www.ovh.com/us/g1868.object_storage_cyberduck

PS. if useful i can create a user so you can check

Thank you

martineau
March 27th, 2017, 06:51 AM
You posted no information about the failure, how do you believe someone can help you!!!!

What error do you get?
Post your configuration.
Add 'device-property "VERBOSE" "YES"' in the changer section.
retry an amcheck.
Post the resulting amcheck debug files.

kladiv
March 27th, 2017, 04:56 PM
Hi,
some of my configs:



define changer "storageobject" {
tpchanger "chg-multi:s3:user1"
device_property "S3_HOST" "storage.bhs3.cloud.ovh.net:443"
device_property "S3_BUCKET_LOCATION" "GRA3"
device-property "VERBOSE" "yes"
device-property "REFRESH_TOKEN" "yes"
device-property "S3_SSL" "yes"
device_property "STORAGE_API" "SWIFT-2.0"
device-property "S3_SERVICE_PATH" "/v1/auth_6f........................................... ....."
# device_property "SWIFT_ACCOUNT_ID" "16......................................."
# device_property "SWIFT_ACCESS_KEY" "vx........................................"
device_property "USERNAME" "n7............................"
device_property "PASSWORD" "vx..........................................."
device_property "TENANT_ID" "6f................................................"
device_property "TENANT_NAME" "16......................."
}
define storage "default" {
autolabel "$c_$3s" empty volume-error
autoflush all
runtapes 1
tapedev "storageobject"
tapetype "container"
}
define tapetype container {
comment "Container Size"
length 1024 gigabytes
}


Log: amlabel.20170328015028.debug



mar mar 28 01:50:28.782008267 2017: pid 31712: thd-0xf13a00: amlabel: pid 31712 ruid 63998 euid 63998 version 3.4.3: start at Tue Mar 28 01:50:28 2017
mar mar 28 01:50:28.782167323 2017: pid 31712: thd-0xf13a00: amlabel: Arguments: user1 User1 slot 1
mar mar 28 01:50:28.782789427 2017: pid 31712: thd-0xf13a00: amlabel: reading config file /etc/amanda/amanda.conf
mar mar 28 01:50:28.784846092 2017: pid 31712: thd-0xf13a00: amlabel: reading config file /etc/amanda/user1/amanda.conf
mar mar 28 01:50:28.877412328 2017: pid 31712: thd-0xf13a00: amlabel: pid 31712 ruid 63998 euid 63998 version 3.4.3: rename at Tue Mar 28 01:50:28 2017
mar mar 28 01:50:28.910084745 2017: pid 31712: thd-0xf13a00: amlabel: Using state file: /etc/amanda/user1/changer
mar mar 28 01:50:28.910691097 2017: pid 31712: thd-0xf13a00: amlabel: /usr/local/share/perl/5.18.2/Amanda/Label.pm:564:info:1000008 Reading label...
mar mar 28 01:50:28.919057862 2017: pid 31712: thd-0xf13a00: amlabel: S3 driver using bucket 'user1', prefix ''
mar mar 28 01:50:28.919166447 2017: pid 31712: thd-0xf13a00: amlabel: curl version: libcurl/7.35.0 OpenSSL/1.0.1f zlib/1.2.8 libidn/1.28 librtmp/2.3
mar mar 28 01:50:28.919176040 2017: pid 31712: thd-0xf13a00: amlabel: curl compiled for OPENSSL
mar mar 28 01:50:28.920094703 2017: pid 31712: thd-0xf13a00: amlabel: Create 1 threads
mar mar 28 01:50:28.920389611 2017: pid 31712: thd-0xf13a00: amlabel: Hostname was NOT found in DNS cache
mar mar 28 01:50:28.980989256 2017: pid 31712: thd-0xf13a00: amlabel: Trying 158.69.169.81...
mar mar 28 01:50:29.061817525 2017: pid 31712: thd-0xf13a00: amlabel: Connected to storage.bhs3.cloud.ovh.net (158.69.169.81) port 443 (#0)
mar mar 28 01:50:29.062627014 2017: pid 31712: thd-0xf13a00: amlabel: successfully set certificate verify locations:
mar mar 28 01:50:29.062652534 2017: pid 31712: thd-0xf13a00: amlabel: CAfile: none
mar mar 28 01:50:29.062666020 2017: pid 31712: thd-0xf13a00: amlabel: CApath: /etc/ssl/certs
mar mar 28 01:50:29.062968357 2017: pid 31712: thd-0xf13a00: amlabel: SSLv3, TLS handshake, Client hello (1):
mar mar 28 01:50:29.155004212 2017: pid 31712: thd-0xf13a00: amlabel: SSLv3, TLS handshake, Server hello (2):
mar mar 28 01:50:29.155108225 2017: pid 31712: thd-0xf13a00: amlabel: SSLv3, TLS handshake, CERT (11):
mar mar 28 01:50:29.160722815 2017: pid 31712: thd-0xf13a00: amlabel: SSLv3, TLS handshake, Server key exchange (12):
mar mar 28 01:50:29.161195884 2017: pid 31712: thd-0xf13a00: amlabel: SSLv3, TLS handshake, Server finished (14):
mar mar 28 01:50:29.161937278 2017: pid 31712: thd-0xf13a00: amlabel: SSLv3, TLS handshake, Client key exchange (16):
mar mar 28 01:50:29.161955942 2017: pid 31712: thd-0xf13a00: amlabel: SSLv3, TLS change cipher, Client hello (1):
mar mar 28 01:50:29.162099696 2017: pid 31712: thd-0xf13a00: amlabel: SSLv3, TLS handshake, Finished (20):
mar mar 28 01:50:29.242967314 2017: pid 31712: thd-0xf13a00: amlabel: SSLv3, TLS change cipher, Client hello (1):
mar mar 28 01:50:29.243150236 2017: pid 31712: thd-0xf13a00: amlabel: SSLv3, TLS handshake, Finished (20):
mar mar 28 01:50:29.243218153 2017: pid 31712: thd-0xf13a00: amlabel: SSL connection using ECDHE-RSA-AES128-GCM-SHA256
mar mar 28 01:50:29.243243653 2017: pid 31712: thd-0xf13a00: amlabel: Server certificate:
mar mar 28 01:50:29.243283676 2017: pid 31712: thd-0xf13a00: amlabel: subject: OU=Domain Control Validated; OU=PositiveSSL Multi-Domain; CN=storage.bhs1.cloud.ovh.net
mar mar 28 01:50:29.243307112 2017: pid 31712: thd-0xf13a00: amlabel: start date: 2017-02-14 00:00:00 GMT
mar mar 28 01:50:29.243326569 2017: pid 31712: thd-0xf13a00: amlabel: expire date: 2018-02-14 23:59:59 GMT
mar mar 28 01:50:29.243414080 2017: pid 31712: thd-0xf13a00: amlabel: subjectAltName: storage.bhs3.cloud.ovh.net matched
mar mar 28 01:50:29.243450875 2017: pid 31712: thd-0xf13a00: amlabel: issuer: C=GB; ST=Greater Manchester; L=Salford; O=COMODO CA Limited; CN=COMODO RSA Domain Validation Secure Server CA
mar mar 28 01:50:29.243469897 2017: pid 31712: thd-0xf13a00: amlabel: SSL certificate verify ok.
mar mar 28 01:50:29.243614038 2017: pid 31712: thd-0xf13a00: amlabel: Hdr Out: POST /v1/auth_6f949adcbcf4461696ec48fe65b647d1 HTTP/1.1
mar mar 28 01:50:29.243628814 2017: pid 31712: thd-0xf13a00: amlabel: Hdr Out: Host: storage.bhs3.cloud.ovh.net
mar mar 28 01:50:29.243640364 2017: pid 31712: thd-0xf13a00: amlabel: Hdr Out: Accept: application/xml
mar mar 28 01:50:29.243652059 2017: pid 31712: thd-0xf13a00: amlabel: Hdr Out: Content-MD5: viEm+0EzygmFLwkcfBXB0Q==
mar mar 28 01:50:29.243663273 2017: pid 31712: thd-0xf13a00: amlabel: Hdr Out: Content-Length: 321
mar mar 28 01:50:29.243675902 2017: pid 31712: thd-0xf13a00: amlabel: Hdr Out: Content-Type: application/xml
mar mar 28 01:50:29.243686487 2017: pid 31712: thd-0xf13a00: amlabel: Hdr Out: Date: Mon, 27 Mar 2017 23:50:28 GMT
mar mar 28 01:50:29.243698894 2017: pid 31712: thd-0xf13a00: amlabel: Hdr Out:
mar mar 28 01:50:29.243767245 2017: pid 31712: thd-0xf13a00: amlabel: Data Out: <?xml version="1.0" encoding="UTF-8"?><auth xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://docs.openstack.org/identity/api/v2.0" tenantId="6f..........................................." tenantName="16................"><passwordCredentials username="n7................" password="vx................................................ ....."/></auth>
mar mar 28 01:50:29.243806296 2017: pid 31712: thd-0xf13a00: amlabel: We are completely uploaded and fine
mar mar 28 01:50:29.373209875 2017: pid 31712: thd-0xf13a00: amlabel: Hdr In: HTTP/1.1 401 Unauthorized
mar mar 28 01:50:29.373324908 2017: pid 31712: thd-0xf13a00: amlabel: Hdr In: Content-Length: 131
mar mar 28 01:50:29.373365589 2017: pid 31712: thd-0xf13a00: amlabel: Hdr In: Content-Type: text/html; charset=UTF-8
mar mar 28 01:50:29.373498121 2017: pid 31712: thd-0xf13a00: amlabel: Hdr In: Www-Authenticate: Swift realm="auth_6f.........................................."
mar mar 28 01:50:29.373523636 2017: pid 31712: thd-0xf13a00: amlabel: Hdr In: WWW-Authenticate: Keystone uri='http://127.0.0.1:5008'
mar mar 28 01:50:29.373542112 2017: pid 31712: thd-0xf13a00: amlabel: Hdr In: X-Trans-Id: tx23ac386bbd8e4584b6a47-0058d9a545
mar mar 28 01:50:29.373608605 2017: pid 31712: thd-0xf13a00: amlabel: Hdr In: X-Openstack-Request-Id: tx23ac386bbd8e4584b6a47-0058d9a545
mar mar 28 01:50:29.373629930 2017: pid 31712: thd-0xf13a00: amlabel: Hdr In: Date: Mon, 27 Mar 2017 23:50:29 GMT
mar mar 28 01:50:29.373715810 2017: pid 31712: thd-0xf13a00: amlabel: Time Offset (remote - local) :0
mar mar 28 01:50:29.373732310 2017: pid 31712: thd-0xf13a00: amlabel: Hdr In:
mar mar 28 01:50:29.373743618 2017: pid 31712: thd-0xf13a00: amlabel: Data In: <html><h1>Unauthorized</h1><p>This server could not verify that you are authorized to access the document you requested.</p></html>
mar mar 28 01:50:29.373815261 2017: pid 31712: thd-0xf13a00: amlabel: Connection #0 to host storage.bhs3.cloud.ovh.net left intact
mar mar 28 01:50:29.373835286 2017: pid 31712: thd-0xf13a00: amlabel: data in 131: <html><h1>Unauthorized</h1><p>This server could not verify that you are authorized to access the document you requested.</p></html>
mar mar 28 01:50:29.373861871 2017: pid 31712: thd-0xf13a00: amlabel: POST https://storage.bhs3.cloud.ovh.net:443/v1/auth_6f.................................... failed with 401/None
mar mar 28 01:50:29.373893028 2017: pid 31712: thd-0xf13a00: amlabel: Device s3:user1 error = 's3_open2 failed: Unknown S3 error (None) (HTTP 401)'
mar mar 28 01:50:29.373930656 2017: pid 31712: thd-0xf13a00: amlabel: Device s3:user1 setting status flag(s): DEVICE_STATUS_DEVICE_ERROR
mar mar 28 01:50:29.376719397 2017: pid 31712: thd-0xf13a00: amlabel: /usr/local/share/perl/5.18.2/Amanda/Label.pm:654:error:1000012 Error reading volume label: s3_open2 failed: Unknown S3 error (None) (HTTP 401).
mar mar 28 01:50:29.377122024 2017: pid 31712: thd-0xf13a00: amlabel: /usr/local/share/perl/5.18.2/Amanda/Label.pm:853:error:1000034 Not writing label.

lillyjacob
March 28th, 2017, 03:20 AM
I think that S3 device support swift . GET service, DELETE bucket, PUT bucket, DELETE object etc are the service provide by it. I f you have any doubt you will get detailed theory about it from dissertation writing services

martineau
March 28th, 2017, 04:43 AM
The S3_SERVICE_PATH should probably be "/v2.0/tokens"

martineau
March 28th, 2017, 04:47 AM
And S3_HOST must be the hostname of the authentication server.

kladiv
April 5th, 2017, 12:56 AM
Hi, any news? Can you support me?

martineau
April 5th, 2017, 04:24 AM
We already support it!!!

I already told you to correctly set S3_SERVICE_PATH and S3_HOST.

kladiv
April 5th, 2017, 10:14 AM
We already support it!!!

I already told you to correctly set S3_SERVICE_PATH and S3_HOST.
Didn't see any answer before.
What values do i need to fill? Why S3_HOST is not correct?

abanghasan
April 8th, 2017, 04:10 AM
hmmm s3 service path, very nice support anyway

kladiv
April 10th, 2017, 07:46 AM
Did more tests, still got errors.
Which values are required for S3_SERVICE_PATH and S3_HOST parameters?

martineau
April 10th, 2017, 08:20 AM
Why do you believe someone know the answer? You are the one using OVH, you are the one that should know the answer!

Did you search the OVH web site for the information? Or you are asking someone else to do it?
Find the authentication server name, find how to get a token.

kladiv
April 10th, 2017, 03:45 PM
Ok,
keystone URL should be: https://auth.cloud.ovh.net/v2.0
I can get a token, but it's 24h valid only.

Which S3 parameters need to use?

martineau
April 11th, 2017, 04:54 AM
The URL to get a token is probably https://auth.cloud.ovh.net/v2.0/tokens
S3_HOST "auth.cloud.ovh.net"
S3_SERVICE_PATH "/v2.0/tokens"

kladiv
April 11th, 2017, 05:05 AM
Hello, thank you!
Did test again. These actual parameters:



tpchanger "chg-multi:s3:user1"
device_property "S3_HOST" "auth.cloud.ovh.net"
device-property "VERBOSE" "yes"
device-property "REFRESH_TOKEN" "yes"
device-property "S3_SSL" "yes"
device_property "STORAGE_API" "SWIFT-2.0"
device-property "S3_SERVICE_PATH" "/v2.0/tokens"
device_property "USERNAME" "n7.............."
device_property "PASSWORD" "vx........................."
device_property "TENANT_ID" "6f........................................."
device_property "TENANT_NAME" "16......................"


amlabel debug log:



mar apr 11 14:00:54.204222435 2017: pid 7727: thd-0x18b8a00: amlabel: pid 7727 ruid 63998 euid 63998 version 3.4.3: start at Tue Apr 11 14:00:54 2017
mar apr 11 14:00:54.204328805 2017: pid 7727: thd-0x18b8a00: amlabel: Arguments: user1 User1 slot 1
mar apr 11 14:00:54.204897418 2017: pid 7727: thd-0x18b8a00: amlabel: reading config file /etc/amanda/amanda.conf
mar apr 11 14:00:54.205203872 2017: pid 7727: thd-0x18b8a00: amlabel: reading config file /etc/amanda/user1/amanda.conf
mar apr 11 14:00:54.236879426 2017: pid 7727: thd-0x18b8a00: amlabel: pid 7727 ruid 63998 euid 63998 version 3.4.3: rename at Tue Apr 11 14:00:54 2017
mar apr 11 14:00:54.254410600 2017: pid 7727: thd-0x18b8a00: amlabel: Using state file: /etc/amanda/user1/changer
mar apr 11 14:00:54.254991428 2017: pid 7727: thd-0x18b8a00: amlabel: /usr/local/share/perl/5.18.2/Amanda/Label.pm:564:info:1000008 Reading label...
mar apr 11 14:00:54.256646987 2017: pid 7727: thd-0x18b8a00: amlabel: S3 driver using bucket 'user1', prefix ''
mar apr 11 14:00:54.256738259 2017: pid 7727: thd-0x18b8a00: amlabel: curl version: libcurl/7.35.0 OpenSSL/1.0.1f zlib/1.2.8 libidn/1.28 librtmp/2.3
mar apr 11 14:00:54.256750407 2017: pid 7727: thd-0x18b8a00: amlabel: curl compiled for OPENSSL
mar apr 11 14:00:54.257573710 2017: pid 7727: thd-0x18b8a00: amlabel: Create 1 threads
mar apr 11 14:00:54.257928494 2017: pid 7727: thd-0x18b8a00: amlabel: Hostname was NOT found in DNS cache
mar apr 11 14:00:54.262217341 2017: pid 7727: thd-0x18b8a00: amlabel: Trying 5.39.17.176...
mar apr 11 14:00:54.264529446 2017: pid 7727: thd-0x18b8a00: amlabel: Connected to auth.cloud.ovh.net (5.39.17.176) port 443 (#0)
mar apr 11 14:00:54.265032366 2017: pid 7727: thd-0x18b8a00: amlabel: successfully set certificate verify locations:
mar apr 11 14:00:54.265046734 2017: pid 7727: thd-0x18b8a00: amlabel: CAfile: none
mar apr 11 14:00:54.265055571 2017: pid 7727: thd-0x18b8a00: amlabel: CApath: /etc/ssl/certs
mar apr 11 14:00:54.265226223 2017: pid 7727: thd-0x18b8a00: amlabel: SSLv3, TLS handshake, Client hello (1):
mar apr 11 14:00:54.282687323 2017: pid 7727: thd-0x18b8a00: amlabel: SSLv3, TLS handshake, Server hello (2):
mar apr 11 14:00:54.282765034 2017: pid 7727: thd-0x18b8a00: amlabel: SSLv3, TLS handshake, CERT (11):
mar apr 11 14:00:54.283563928 2017: pid 7727: thd-0x18b8a00: amlabel: SSLv3, TLS handshake, Server key exchange (12):
mar apr 11 14:00:54.285153131 2017: pid 7727: thd-0x18b8a00: amlabel: SSLv3, TLS handshake, Server finished (14):
mar apr 11 14:00:54.285923599 2017: pid 7727: thd-0x18b8a00: amlabel: SSLv3, TLS handshake, Client key exchange (16):
mar apr 11 14:00:54.285943540 2017: pid 7727: thd-0x18b8a00: amlabel: SSLv3, TLS change cipher, Client hello (1):
mar apr 11 14:00:54.286057305 2017: pid 7727: thd-0x18b8a00: amlabel: SSLv3, TLS handshake, Finished (20):
mar apr 11 14:00:54.288353893 2017: pid 7727: thd-0x18b8a00: amlabel: SSLv3, TLS change cipher, Client hello (1):
mar apr 11 14:00:54.288462923 2017: pid 7727: thd-0x18b8a00: amlabel: SSLv3, TLS handshake, Finished (20):
mar apr 11 14:00:54.288499990 2017: pid 7727: thd-0x18b8a00: amlabel: SSL connection using ECDHE-RSA-AES128-GCM-SHA256
mar apr 11 14:00:54.288520767 2017: pid 7727: thd-0x18b8a00: amlabel: Server certificate:
mar apr 11 14:00:54.288547105 2017: pid 7727: thd-0x18b8a00: amlabel: subject: OU=Domain Control Validated; CN=auth.cloud.ovh.net
mar apr 11 14:00:54.288565836 2017: pid 7727: thd-0x18b8a00: amlabel: start date: 2015-04-20 09:14:39 GMT
mar apr 11 14:00:54.288580315 2017: pid 7727: thd-0x18b8a00: amlabel: expire date: 2018-04-20 09:14:39 GMT
mar apr 11 14:00:54.288641854 2017: pid 7727: thd-0x18b8a00: amlabel: subjectAltName: auth.cloud.ovh.net matched
mar apr 11 14:00:54.288665647 2017: pid 7727: thd-0x18b8a00: amlabel: issuer: C=BE; O=GlobalSign nv-sa; CN=AlphaSSL CA - SHA256 - G2
mar apr 11 14:00:54.288680561 2017: pid 7727: thd-0x18b8a00: amlabel: SSL certificate verify ok.
mar apr 11 14:00:54.288763223 2017: pid 7727: thd-0x18b8a00: amlabel: Hdr Out: POST /v2.0/tokens HTTP/1.1
mar apr 11 14:00:54.288809804 2017: pid 7727: thd-0x18b8a00: amlabel: Hdr Out: Host: auth.cloud.ovh.net
mar apr 11 14:00:54.288820394 2017: pid 7727: thd-0x18b8a00: amlabel: Hdr Out: Accept: application/xml
mar apr 11 14:00:54.288829927 2017: pid 7727: thd-0x18b8a00: amlabel: Hdr Out: Content-MD5: viEm+0EzygmFLwkcfBXB0Q==
mar apr 11 14:00:54.288839324 2017: pid 7727: thd-0x18b8a00: amlabel: Hdr Out: Content-Length: 321
mar apr 11 14:00:54.288848315 2017: pid 7727: thd-0x18b8a00: amlabel: Hdr Out: Content-Type: application/xml
mar apr 11 14:00:54.288857354 2017: pid 7727: thd-0x18b8a00: amlabel: Hdr Out: Date: Tue, 11 Apr 2017 12:00:54 GMT
mar apr 11 14:00:54.288866643 2017: pid 7727: thd-0x18b8a00: amlabel: Hdr Out:
mar apr 11 14:00:54.288912939 2017: pid 7727: thd-0x18b8a00: amlabel: Data Out: <?xml version="1.0" encoding="UTF-8"?><auth xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://docs.openstack.org/identity/api/v2.0" tenantId="6f................................." tenantName="16............................."><passwordCredentials username="n7..............." password="vx........................."/></auth>
mar apr 11 14:00:54.288927124 2017: pid 7727: thd-0x18b8a00: amlabel: We are completely uploaded and fine
mar apr 11 14:00:54.301906427 2017: pid 7727: thd-0x18b8a00: amlabel: Hdr In: HTTP/1.1 400 Bad Request
mar apr 11 14:00:54.302021256 2017: pid 7727: thd-0x18b8a00: amlabel: Hdr In: Vary: X-Auth-Token
mar apr 11 14:00:54.302056473 2017: pid 7727: thd-0x18b8a00: amlabel: Hdr In: Content-Type: application/json
mar apr 11 14:00:54.302189509 2017: pid 7727: thd-0x18b8a00: amlabel: Hdr In: Content-Length: 258
mar apr 11 14:00:54.302214888 2017: pid 7727: thd-0x18b8a00: amlabel: Hdr In: Date: Tue, 11 Apr 2017 12:00:54 GMT
mar apr 11 14:00:54.302369314 2017: pid 7727: thd-0x18b8a00: amlabel: Time Offset (remote - local) :0
mar apr 11 14:00:54.302392053 2017: pid 7727: thd-0x18b8a00: amlabel: Hdr In:
mar apr 11 14:00:54.302405205 2017: pid 7727: thd-0x18b8a00: amlabel: Data In: {"error": {"message": "Expecting to find application/json in Content-Type header - the server could not comply with the request since it is either malformed or otherwise incorrect. The client is assumed to be in error.", "code": 400, "title": "Bad Request"}}
mar apr 11 14:00:54.302445233 2017: pid 7727: thd-0x18b8a00: amlabel: Connection #0 to host auth.cloud.ovh.net left intact
mar apr 11 14:00:54.302466336 2017: pid 7727: thd-0x18b8a00: amlabel: data in 258: {"error": {"message": "Expecting to find application/json in Content-Type header - the server could not comply with the request since it is either malformed or otherwise incorrect. The client is assumed to be in error.", "code": 400, "title": "Bad Request"}}
mar apr 11 14:00:54.302491678 2017: pid 7727: thd-0x18b8a00: amlabel: POST https://auth.cloud.ovh.net/v2.0/tokens failed with 400/None
mar apr 11 14:00:54.302519950 2017: pid 7727: thd-0x18b8a00: amlabel: Device s3:user1 error = 's3_open2 failed: Unknown S3 error (None) (HTTP 400)'
mar apr 11 14:00:54.302558571 2017: pid 7727: thd-0x18b8a00: amlabel: Device s3:user1 setting status flag(s): DEVICE_STATUS_DEVICE_ERROR
mar apr 11 14:00:54.305000650 2017: pid 7727: thd-0x18b8a00: amlabel: /usr/local/share/perl/5.18.2/Amanda/Label.pm:654:error:1000012 Error reading volume label: s3_open2 failed: Unknown S3 error (None) (HTTP 400).
mar apr 11 14:00:54.305411719 2017: pid 7727: thd-0x18b8a00: amlabel: /usr/local/share/perl/5.18.2/Amanda/Label.pm:853:error:1000034 Not writing label.


Reading Doc https://www.ovh.com/us/g1872.managing_tokens this should be cURL method:
$ curl -X POST $OS_AUTH_URL/tokens -H "Content-Type: application/json" -d '{"auth": {"tenantName": "'$OS_TENANT_NAME'", "passwordCredentials": {"username": "'$OS_USERNAME'", "password": "'$OS_PASSWORD'"}}}' | python -mjson.tool

Maybe Content-Type: application/json required?

martineau
April 11th, 2017, 05:35 AM
older keystone supported both xml and json.
Amanda is using xml.
xml support was removed in Juno !!!

amanda must be enhanced to use json !!!

kladiv
April 11th, 2017, 05:56 AM
older keystone supported both xml and json.
Amanda is using xml.
xml support was removed in Juno !!!

amanda must be enhanced to use json !!!
Ok :)
I hope to see json content-type support in the next release

martineau
May 4th, 2017, 06:42 AM
It's in 3.4.4

kladiv
May 4th, 2017, 03:59 PM
It's in 3.4.4
Nice!! I'm going to test it asap