[Bug]: Error invoking barman-cloud-wal-archive about cloudnative-pg HOT 8 CLOSED

@sxd Could you please reopen this issue? I can't! It is working for me now, but only after I disabled:

wal:
  compression: gzip
  encryption: AES256
data:
  compression: gzip
  encryption: AES256
  immediateCheckpoint: false
  jobs: 2

Maybe not all of this is needed, but when I disabled these parts by commenting them out, everything started working.

from cloudnative-pg.

@sxd I am sorry, but I cannot follow. If there is an invalid request, then that's an invalid request from the outside not from within the object store. And like I wrote: With the given configuration the operator is able to create buckets but not to push anything though this user has all the rights available and manual pushes with the given credentials work just fine. If the credentials were invalid, how could then a bucket be created?

from cloudnative-pg.

@BartoszGiza Encryption might be a reason. My Ceph setup is only an example for my playground at home. Either way, if encryption is the case, then the error message should reflect this. Currently it is such a generic message ... which could mean anything. Better - of course - would be a way to figure out if backend encryption is available and if it is not, then the operator should fail.

from cloudnative-pg.

Hello @Jeansen

This is an error with your object store, look for this message:

"2024-04-15 22:17:34,880 [3398] ERROR: Barman cloud WAL archiver exception: An error occurred (InvalidRequest) when calling the PutObject operation: None"

So please look into your object store and check why it's failing with that InvalidRequest with the PutObject, in the past this has been due to some permission issue.

Closing for now, feel free to reopen if needed.

Regards!

from cloudnative-pg.

Hey @sxd, thanks for the super quick reply. I'd doubt it is an permission issue. The user in question has all the permission possible. Like I wrote, the operator is even able to create a bucket with the given secret an access keys, if the specified one is not yet created. And when I check the bucket, it belongs to the right user. If I put some object in this bucket manually with the same user, that is access key and secret key, then this works without any problem.

from cloudnative-pg.

@Jeansen then the access key and/or secret key is not well written?
As I said, the problem here isn't on the operator, it's the object store replying InvalidRequest
Get inside the pod and try executing the command that it's already there in the logs you pasted and you should be able to run it manually and check

Regards,

from cloudnative-pg.

@Jeansen Thank you very much. I was struggling with the same issue for couple of days.
I haven't thought to disable those settings.

@sxd and i think it is problem of operator. I was actually able to manually push wal files with barman-cloud-wal-archive from pod but via controller it didn't work.
For whatever reason i think compression setting breaks something

from cloudnative-pg.

I think it might be actually issue with encryption parameter which if not mistaken tells S3 storage to use enable backend encryption. So it depends of Backend implementation

from cloudnative-pg.