Project

General

Profile

Actions
Copy link

Defect #44375

open

Concurrency problem in project deletion / project marking for deletion

Added by Felix Schäfer 5 days ago. Updated 5 days ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Database
Target version:
-
Resolution:
Affected version:
7.0.0

Description

The problem we noticed was:
- a user selects some projects to be bulk deleted and submits the request
- other projects than the selected projects get marked as STATUS_SCHEDULED_FOR_DELETION
- the correct originally select projects are deleted

Our analysis showed that between selecting the projects in the ProjectsController#bulk_delete and updating the projects with the STATUS_SCHEDULED_FOR_DELETION in DestroyProjectJob.schedule another previous DestroyProjectJob might change the Project tree, which then leads to project.self_and_descendants in DestroyProjectJob.schedule to select the wrong projects.

Files

44375-atomic_mark_project_scheduled_for_deletion.patch (6.14 KB) 44375-atomic_mark_project_scheduled_for_deletion.patch Felix Schäfer, 2026-08-25 16:26
Actions
Copy link

Also available in: Atom PDF