Re: [Duplicity-talk] OVHCloud's S3

[Kenneth Loafman]

Hi,

The last time this happened was on Amazon S3 and the problem was that the boto3 and botocore clients were very old.  I see you are only a few versions off the latest, so I will suggest we first do an upgrade.

1. First purge python3-botocore and python3-boto3 using yum (I think), then,
2. $ sudo python3.11 -m pip install --U boto3 botocore
3. try again and report back with a full traceback if not fixed.

...Ken

On Wed, May 10, 2023 at 2:20 PM Troels Arvin via Duplicity-talk <duplicity-talk@nongnu.org> wrote:

Hello,

I'm trying to make Duplicity work with OVHCloud's S3, but I run into an
error. Duplicity version: 1.2.2 (part of Fedora Linux 38).

I’ve set up an S3 container in OVHCloud, and it works when I use “s3cmd”:

[me@pc ~]$ s3cmd ls
2023-05-07 16:02  s3://backupcontainer-pc

This is the error I get when running Duplicty:

File "/usr/lib/python3.11/site-packages/botocore/client.py", line 960,
in _make_api_call
   raise error_class(parsed_response, operation_name)
  botocore.exceptions.ClientError: An error occurred (400) when calling
the HeadBucket operation: Bad Request

This is the command I use (altough I add many more --include/–exclude
parameters):

duplicity --verbosity Debug --no-print-statistics --include /usr/local
--include /root --exclude ** --asynchronous-upload --s3-region-name WAW
--s3-endpoint-url https://s3.waw.io.cloud.ovh.net / s3://backupcontainer-pc

When running the command, AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY
are set using the same values which work with s3cmd.

Related software packages on the system:
python3-botocore-1.29.111-1.fc38.noarch
python3-boto3-1.26.111-1.fc38.noarch

Any ideas?

--
Troels


_______________________________________________
Duplicity-talk mailing list
Duplicity-talk@nongnu.org
https://lists.nongnu.org/mailman/listinfo/duplicity-talk