I've been using Libcloud for sometime now with the generic s3 object storage driver. On the backend its connecting to a CEPH deployment. Things had been going great but this past week one of my clients couldn't upload new objects. The error I got was rather perplexing:
ERROR: Put of <REDACTEDFILEPATH> failed (b'<?xml version="1.0" encoding="UTF-8"?><Error><Code>SignatureDoesNotMatch</Code><RequestId>tx000008072ceace0f452a8-006533d12b-1d3d3-east</RequestId><HostId>1d3d3-east-iso</HostId></Error>') I eventually used awscli and it was able to upload the object without issue, so this pointed my problem being with the custom metadata I attached to the object. Through trial and error I found the metadata field that triggered the error and the specific set of characters in that field. The root problem is two consecutive space characters. I didn't see any mention of two spaces being illegal here: https://docs.aws.amazon.com/AmazonS3/latest/userguide/UsingMetadata.html Is there a set of rules that metadata must conform to for Libcloud? Is this a bug? Thanks for your consideration. Brian Sullivan
