Delete domain operation may have atomicity problems
Bug #1438915 reported by
Rodrigo Duarte
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Identity (keystone) |
Triaged
|
Low
|
Deepti Ramakrishna |
Bug Description
This bug was first discussed in the Recursive Deletion spec: https:/
Currently, when deleting a domain, all projects inside that domain are also deleted. When we have a hierarchy of projects this may cause inconsistencies since the operations are not atomic [1] (each level of the hierarchy is deleted in a separate transaction).
Two possible solutions to explore are:
1 - Use the concept of logical deletion
2 - As a first step list all project's id to be deleted and trigger one delete transaction with all ids
[1] https:/
description: | updated |
Changed in keystone: | |
status: | New → Triaged |
importance: | Undecided → Low |
Changed in keystone: | |
assignee: | nobody → Deepti Ramakrishna (dramakri) |
To post a comment you must log in.