Percona Operator mysql: Value for x-amz-checksum-crc32c header is invalid on pitr pod

[jonathon2nd]

Fresh helm instalation

REPO URL: https://percona.github.io/percona-helm-charts/
CHART: pxc-db:1.14.3
CHART: pxc-operator:1.14.1

Logs from percona/percona-xtradb-cluster-operator:1.14.0-pxc8.0-backup-pxb8.0.35

2024/06/07 18:01:12 run binlog collector
2024-06-07T11:01:13.890069886-07:00 2024/06/07 18:01:13 Reading binlogs from pxc with hostname= mysql-01-pxc-db-pxc-0.mysql-01-pxc-db-pxc.percona-mysql-op.svc.cluster.local
2024-06-07T11:01:14.012974199-07:00 2024/06/07 18:01:14 Starting to process binlog with name binlog.000002
2024-06-07T11:01:14.773274568-07:00 2024/06/07 18:01:14 ERROR: collect binlog files: manage binlog: put binlog.000002 object: put object binlog_1717782524_167aee546bf864cf19bb33c8c4ee9da9: Value for x-amz-checksum-crc32c header is invalid.

Values

backup:
  enabled: true
  image:
    repository: percona/percona-xtradb-cluster-operator
    tag: 1.14.0-pxc8.0-backup-pxb8.0.35
  pitr:
    enabled: true
    storageName: s3-wasabi
    timeBetweenUploads: 60
    timeoutSeconds: 60
    resources:
      requests: {}
      limits: {}
  storages: 
    s3-wasabi:
      type: s3
      s3:
        bucket: 01-percona-mysql-backup
        credentialsSecret: cluster1-s3-credentials
        endpointUrl: https://s3.ca-central-1.wasabisys.com/
        prefix: ""

I also tried with 1.14.0-pxc8.0.36-backup-pxb8.0.35, same error.
I also get the same error when I add region: ca-central-1

I have looked at https://docs.percona.com/percona-operator-for-mysql/pxc/backups-storage.html and https://docs.percona.com/percona-operator-for-mysql/pxc/operator.html#backup-section as well.

[jonathon2nd]

Ok even more confusing, the backup job on percona/percona-xtradb-cluster-operator:1.14.0-pxc8.0-backup-pxb8.0.35 ran successfully.

[mr-kelly]

Ok even more confusing, the backup job on percona/percona-xtradb-cluster-operator:1.14.0-pxc8.0-backup-pxb8.0.35 ran successfully.

Me too, I use Wasabi as well. Seems like some S3 features cannot be satisfied in Wasbi