Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[stable29] fix: Make user removal more resilient #48588

Merged
merged 3 commits into from
Oct 17, 2024

Conversation

backportbot[bot]
Copy link

@backportbot backportbot bot commented Oct 7, 2024

Backport of #47896

Warning, This backport's changes differ from the original and might be incomplete ⚠️

Todo

  • Review and resolve any conflicts
  • Amend HEAD commit to remove the line stating to skip CI

Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports.

@backportbot backportbot bot requested review from artonge, come-nc and susnux October 7, 2024 09:35
@backportbot backportbot bot added this to the Nextcloud 29.0.8 milestone Oct 7, 2024
@backportbot backportbot bot force-pushed the backport/47896/stable29 branch from fb94282 to 236bf80 Compare October 7, 2024 09:36
@susnux
Copy link
Contributor

susnux commented Oct 8, 2024

/cherry-pick 902fb8f

susnux and others added 3 commits October 15, 2024 16:50
Currently there is a problem if an exception is thrown in `User::delete`,
because at that point the user is already removed from the backend,
but not all data is deleted.

There is no way to recover from this state, as the user is gone no information is available anymore.
This means the data is still available on the server but can not removed by any API anymore.

The solution here is to first set a flag and backup the user home,
this can be used to recover failed user deletions in a way the delete can be re-tried.

Signed-off-by: Ferdinand Thiessen <opensource@fthiessen.de>
Signed-off-by: Ferdinand Thiessen <opensource@fthiessen.de>
Signed-off-by: provokateurin <kate@provokateurin.de>
@susnux susnux force-pushed the backport/47896/stable29 branch from 236bf80 to 7dc1c7f Compare October 15, 2024 14:50
@susnux susnux marked this pull request as ready for review October 15, 2024 14:50
@susnux susnux requested a review from provokateurin October 15, 2024 14:50
@susnux susnux enabled auto-merge October 17, 2024 16:00
@susnux susnux merged commit 658aa1a into stable29 Oct 17, 2024
179 of 181 checks passed
@susnux susnux deleted the backport/47896/stable29 branch October 17, 2024 16:21
@Altahrim Altahrim mentioned this pull request Oct 30, 2024
4 tasks
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.

4 participants