yahoo-eng-team team mailing list archive

[Rodrigo Duarte <rodrigodsousa@xxxxxxxxx>]

Public bug reported:

This bug was first discussed in the Recursive Deletion spec:
https://review.openstack.org/#/c/148730/

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://github.com/openstack/keystone/blob/master/keystone/resource/core.py#L470-L498

** Affects: keystone
     Importance: Undecided
         Status: New

** Description changed:

+ This bug was first discussed in the Recursive Deletion spec:
+ https://review.openstack.org/#/c/148730/
+ 
  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://github.com/openstack/keystone/blob/master/keystone/resource/core.py#L470-L498

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1438915

Title:
  Delete domain operation may have atomicity problems

Status in OpenStack Identity (Keystone):
  New

Bug description:
  This bug was first discussed in the Recursive Deletion spec:
  https://review.openstack.org/#/c/148730/

  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://github.com/openstack/keystone/blob/master/keystone/resource/core.py#L470-L498

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1438915/+subscriptions