SOBR Failing But 10:00 Email Shows All Fine

[jlester]

Ticket #05989374

We're having an issue with v12 and a Backblaze S3 repo where the jobs start failing with the message: Scale-out repository rescan is required: performance tier is not synchronized with capacity tier. A rescan does fix it, but we want to get at what is causing it. The really concerning thing is that the 10:00 email that going out about the SOBR status shows everything is fine, even when the earlier jobs are failing due to that error.

[veremin]

I believe that the email report only shows the persistent issues (not intermittent ones that got fixed automatically later on), but it never harms verifying the assumption with the support team. Thanks!

[jlester]

It seems like there's definitely something wrong, but it's hard to tell from the reports. The sync has been going for over an hour now and we're on 10G Internet. Better reporting for the SOBR offloads would be really helpful. I see some other posts saying the same thing recently.

[veremin]

Let's support team investigate the issue further and come up with the final conclusions. Thanks!