Yes, I didn't update anything. The issue started presenting itself a month 
ago, and after several attempts the jobs tended to finally work. Last night 
was the first time none of them worked.
No idea what might've caused it on Amazon side. They usually warn about any 
sort of breaking changes months in advance.

>  Listing the Buckets is not sufficient, because the client might see a 
bucket, but does not have (write) access to it.  
The current (supposedly broken) and the proposed (in the PR) methods 
succeed without ever checking for write permissions too, don't they?

Either way, sorry for being antagonistic towards the solution in the PR, it 
does feel like a project of this scale deserves something better thought 
out. I'll let you know if I come up with anything myself.

On Friday, November 20, 2020 at 7:32:21 PM UTC+3 Andreas Rogge wrote:

> Am 20.11.20 um 17:11 schrieb Dmitry Ponkin:
> > I just patched 19.2.7 to use marker.bareos and put that file into every
> > bucket. It's a subpar solution at best and should not be merged.
>
> If you didn't upgrade Bareos or libdroplet and it suddenly broke, I
> guess it was the other end breaking compatiblility. Do you have any
> idea, what change at Amazon's broke access to "/" in the buckets?
>
> Listing the Buckets is not sufficient, because the client might see a
> bucket, but does not have (write) access to it.
>
> Best Regards,
> Andreas
>
> -- 
> Andreas Rogge [email protected]
> Bareos GmbH & Co. KG Phone: +49 221-630693-86 <+49%20221%2063069386>
> http://www.bareos.com
>
> Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646
> Komplementär: Bareos Verwaltungs-GmbH
> Geschäftsführer: S. Dühr, M. Außendorf, J. Steffens, Philipp Storz
>

-- 
You received this message because you are subscribed to the Google Groups 
"bareos-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/bareos-users/e0e7358f-62ad-4859-a782-438eff6db3b0n%40googlegroups.com.

Reply via email to