An error occurred while fetching the assigned milestone of the selected merge_request.
Make nested groups deletion synchronous to avoid potential race
There may be a potential race condition in the group deletion. Suppose there is a namespace test
with nested group foo
:
- Namespace
test
is queued for deletion - Namespace
test
schedulesfoo
for deletion - Namespace
test
is destroyed - Namespace
foo
finds no parent, so it may fail
Didn't have time to write a spec for this, but I wanted to raise this as a potential issue.
Merge request reports
Activity
changed milestone to %9.0
@stanhu makes total sense, thanks
added 870 commits
-
bac125d4...8b855eaf - 868 commits from branch
master
- 3129dd50 - Make nested groups deletion synchronous to avoid potential race
- 334591dd - Include nested group into destroy_service_spec
-
bac125d4...8b855eaf - 868 commits from branch
enabled an automatic merge when the pipeline for 334591dd succeeds
Please register or sign in to reply