On 14.05.2023 14:48, Troels Arvin via Duplicity-talk wrote:
> File "/usr/lib64/python3.11/site-packages/duplicity/backends/s3_boto3_backend.py", line 174, in _list
> self.reset_connection()
> File "/usr/lib64/python3.11/site-packages/duplicity/backends/s3_boto3_backend.py", line 101, in reset_connection
> error_resource = bce.response[u'Error'][u'Resource']
> ~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^
> KeyError: 'Resource'
@Ken
maybe the easiest would be just to print the *whole stack* instead of just the one error at that point? ..sunny regards ede
@ede: He's printed the whole stack trace and we know where the error comes from. The problem is that S3 maps the 400 error to about a dozen different errors. I was trying to use the S3 docs to get full detail on which of the ambiguous errors they were referring to. It appears that OVH does not return the same info. I really have no idea why not if they claim to be S3 compatible.
@Troels: I want you to do this,
- Remove lines #101 and #105 in your patched s3_boto3_backend.py (error_resource) then,
- Run duplicity with "-v debug" and save the entire log to file.
- Attach, do not copy paste, the log file to your reply.
...Thanks,
...Ken