failed to delete snapshot - "bucket does not exist" (400) when deleting snapshots from S3 datastore

[frederik.rooms]

I started to sync my local datastore via pull direction to a Wasabi S3 bucket. I selected 'Remove Vanished' in the configuration but I got error messages of the snapshots it wanted to delete. I got the error message,"failed to delete snapshot - "bucket does not exist" (400)" for each snapshot the pbs wanted to remove. I thought it had to do something with the bucket settings but apparantly nothing is activated and I just have the default settings in Wasabi. Unless something is not right in the Wasabi documentation?

When I unchecked the 'Remove Vanished', the errors were gone but logically the deleted snapshots from my local datastore were still appearing in my wasabi datastore. When I delete the snapshot manually I got the message again in the dialog. I cannot figure out what goes wrong and where the source of my problem is located.

 

[Chris]

Hi, please try to run proxmox-backup-manager s3 check <s3-endpoint-id> <bucket> and post the full output you get. Also, if not sensitive information and not publicly accessible (which is not advised in any case) please share your exact bucket name.

On a hunch I suspect that you might either have some provider side access misconfiguration (maybe double check your access key permissions to remove objects with an independent s3 client) or an error in the s3 endpoint config (double check endpoint url, region and path-style), although the latter being less likely given that other operations seem to work just fine.

Further, do you have some provider specific retention settings which might block object deletion?

 

[frederik.rooms]

Hi, please try to run proxmox-backup-manager s3 check <s3-endpoint-id> <bucket> and post the full output you get. Also, if not sensitive information and not publicly accessible (which is not advised in any case) please share your exact bucket name.

On a hunch I suspect that you might either have some provider side access misconfiguration (maybe double check your access key permissions to remove objects with an independent s3 client) or an error in the s3 endpoint config (double check endpoint url, region and path-style), although the latter being less likely given that other operations seem to work just fine.

Further, do you have some provider specific retention settings which might block object deletion?

Hi

Thanks for helping me out but for PBS 4.1.1 it seems that your check does not work in my case. I could not use your command since it gave me errors complaining about the length of the endpoint (I replaced the templates by values). When removing the bucketname in the endpoint I got the message that the config does not exist. When I get the list of endpoints I got this response below, which I used as source to complete you cmd check. So it is available but I could not match it with your request.



I solved my initial question by removing the style path. It seems that style path is needed to complete the creation of a datastore (got error connecting to bucket when creating datastore with these credentials) but when you start using the bucket I had to remove the path style in order to make the snapshot deletion go well.

 

[Chris]

Hi

Thanks for helping me out but for PBS 4.1.1 it seems that your check does not work in my case. I could not use your command since it gave me errors complaining about the length of the endpoint (I replaced the templates by values). When removing the bucketname in the endpoint I got the message that the config does not exist. When I get the list of endpoints I got this response below, which I used as source to complete you cmd check. So it is available but I could not match it with your request.

There seems to be a misunderstanding, the <s3-endpoint-id> in your case is wasabi-backup, not the endpoint url.

I solved my initial question by removing the style path. It seems that style path is needed to complete the creation of a datastore (got error connecting to bucket when creating datastore with these credentials) but when you start using the bucket I had to remove the path style in order to make the snapshot deletion go well.

Glad it works now as expected.