Ceph » rgw

When using Cloud Transition with Backblaze B2's S3 offering, the logs show the following errors when lifecycle executes to transition an object to the provider.

debug 2025-09-29T16:39:10.458+0000 7f7b29f82640 20 lifecycle: ERROR: orule.process() returned ret=-22 thread=wp_thrd: 0, 2 bucket=rgw-test-a18bb949-efe7-4c54-9896-da2c7a1fae04
debug 2025-09-29T16:39:10.774+0000 7f7b29f82640 0 lifecycle: ERROR: fail to complete request, ret = -22
debug 2025-09-29T16:39:10.774+0000 7f7b29f82640 0 lifecycle: ERROR: failed to transition object ret=-22
debug 2025-09-29T16:39:10.774+0000 7f7b29f82640 0 lifecycle: ERROR: failed to transfer object(rgw-test-put-000051.dat) to the cloud endpoint(https://s3.us-east-005.backblazeb2.com) ret=-22
debug 2025-09-29T16:39:10.774+0000 7f7b29f82640 0 lifecycle: ERROR: failed to transition obj(key:rgw-test-put-000051.dat) to cloud (r=-22)
debug 2025-09-29T16:39:10.774+0000 7f7b29f82640 0 lifecycle: ERROR: remove_expired_obj :rgw-test-a18bb949-efe7-4c54-9896-da2c7a1fae04[b786ab23-d551-4fca-bf7b-f0d5134e6677.1557690.1]):rgw-test-put-000051.dat (22) Invalid argument wp_thrd: 0, 2

A bpftrace of the rgw daemon shows me the following header is missing as part of the signature

<Error>
<Code>InvalidRequest</Code>
<Message>header 'x-amz-content-sha256' must be included in signature</Message>
</Error>

From the S3 specs this header seems to be required, but also optional under certain conditions.
https://docs.aws.amazon.com/AmazonS3/latest/API/sig-v4-header-based-auth.html