Backup to tebi not working

[girish]

I am also using a prefix. What is the error you are getting?

[robi]

@girish same as OP, seems to be a local issue, as the bucket has the prefix created and what looks like the first app backup, but then errors.

[girish]

@robi ah, it could be that old (invalid) backups are not found. I think if you delete the Site and add it again, it will work . Can you try that?

[robi]

@girish uhh sure, but this would be a great use case for a clone backup config to an edit screen for changes then save.

[robi]

@girish created new config, started backup, began with first app, then it decided to delete old entries, then it failed:

Maybe it's an rsync vs tgz issue now, in combination with the former path "/" issue?

[girish]

@robi said in Old backup not found when updating app:

Maybe it's an rsync vs tgz issue now, in combination with the former path "/" issue?

Oh, this could be. Testing

[girish]

@robi I could reproduce it. There is a bug in the tebi service. It is listing directories as part of listObjectsV2 API call. S3 has no concept of directories, just key/value pairs.

I have reported this to them.

[girish]

@robi they replied to me saying they won't fix it . They did tell me why, but you might want to reach out to them for more info, don't want to breach confidentiality.

[robi]

Whoa, unexpected.

One could also say that it's not a bug, as object stores don't distinguish files from directories, as they're all objects. It's the implementation that does.

So it may be more likely that the s3 client/driver/config needs to compensate.

ex. Cyberduck works fine.

[robi]

@girish Can you send me a note in the chat here or an email as to what they said?