Init storage: write init file: save during split-merge mw: upload to S3: operation error S3: PutObject, https response error StatusCode: 400, RequestID: oj3keqKA, HostID: , api error InvalidArgument: The specified header is not valid in this context

Description:

After updating MongoDB to version 8.0.17-6, the backup with PBM 2.9.1 stopped working.
I decided to update psmdb-operator to 1.21.3, psmdb-db to 1.21.2, and PBM to 2.11.0.
However, S3 compatibility was lost. I see that a new version 2.12.0 has been released, where type: minio was added for compatibility with older APIs:
https://perconadev.atlassian.net/browse/PBM-1610
But the update also doesn’t help. Is there any solution?

Steps to Reproduce:

To run a logical backup with the specified versions.
yaml

      storages:
        s3-backup:
          type: minio
          minio:
            bucket: s3-pp-mongodb-backup
            region: ru-msk
            endpointUrl: https://s3.mo.ru
            credentialsSecret: mongodb-backup-secret
            retryer:
              numMaxRetries: 3
              minRetryDelay: 30ms
              maxRetryDelay: 5m

Version:

psmdb-operator 1.21.3
psmdb-db 1.21.2
pbm 2.11.0\2.12.0

Logs:

init storage: write init file: save during split-merge mw: upload to S3: operation error S3: PutObject, https response error StatusCode: 400, RequestID: oj3keqKA, HostID: , api error InvalidArgument: The specified header is not valid in this context

Expected Result:

backup status is ready

Actual Result:

backup status is error

I see a task titled “Implement Native MinIO Support for backup storage” in version 1.22.0 of the operator.

That’s correct. It should be available soon and fix your issue. By that time you can’t use ‘minio’ type within the operator’s CR.