Skip to content

[stable32] fix(files_external): propagate child copy failures in AmazonS3::copy() - #65006

Open
backportbot[bot] wants to merge 1 commit into
stable32from
backport/63123/stable32
Open

backportbot[bot] wants to merge 1 commit into
stable32from
backport/63123/stable32

Conversation

@backportbot

@backportbot backportbot Bot commented Oct 2, 2026

Copy link
Copy Markdown

Backport of PR #63123

When copying a directory, copy() discarded the return values of its
recursive calls and always returned true. rename() relies on that value,
so a failed copy still led to rmdir() on the source: every file in the
directory was deleted, the destination stayed empty, and the UI reported
success.

This is reachable whenever a provider rejects CopyObject for objects it
otherwise serves — Hetzner Object Storage answers 501 NotImplemented for
SSE-C encrypted objects, which makes every single child copy fail.

Signed-off-by: Robert Niederreiter <rnix@squarewave.at>

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant