Bug #41412
closed
multisite: ENOENT errors from FetchRemoteObj causing bucket sync to stall without retry
Added by Casey Bodley over 4 years ago.
Updated over 4 years ago.
Backport:
luminous mimic nautilus
Description
BucketSyncSingleEntry is supposed to filter out ENOENT (404 Not Found) errors, but there is one case where it accidentally returns that as a fatal error up the stack to DataSyncSingleEntry. DataSyncSingleEntry misinterprets ENOENT to mean that the bucket doesn't exist, so it doesn't schedule the failed bucket sync for retries.
- Status changed from New to Fix Under Review
- Assignee set to Casey Bodley
- Pull request ID set to 29856
- Status changed from Fix Under Review to 7
- Status changed from 7 to Pending Backport
- Copied to Backport #41626: luminous: multisite: ENOENT errors from FetchRemoteObj causing bucket sync to stall without retry added
- Copied to Backport #41627: nautilus: multisite: ENOENT errors from FetchRemoteObj causing bucket sync to stall without retry added
- Copied to Backport #41628: mimic: multisite: ENOENT errors from FetchRemoteObj causing bucket sync to stall without retry added
- Status changed from Pending Backport to Resolved
While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".
Also available in: Atom
PDF