Project

General

Profile

Bug #654

Delete operations fail during orchestration

Added by Paul Kelly over 8 years ago. Updated about 8 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Orchestration
Target version:
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
Team Backlog:
Fixed in Releases:
Found in Releases:

Description

This needs some investigation but I believe that if a delete operation fails then the database transaction COMMITS. This appears to be because the Orchestration#destroy method is not within a transaction and the ROLLBACK is just an ordinary exception.

It may be that this is more or less complicated than that but this what I have seen.

I admit that I cannot see how this is possible, so maybe I am wrong.

Associated revisions

Revision 822eef5a (diff)
Added by Paul Kelly about 8 years ago

Fixes #654 - Delete ROLLBACK should be in transaction block

Signed-off-by: Paul Kelly <>

History

#1 Updated by Paul Kelly about 8 years ago

After some investigation it appears that the structure of the code is such that the destroy teardown is occurring AFTER the commit has been executed. The obvious solution is to perform the rollback operations in an after_delete method as this ensures that we are within the transactional block.

#2 Updated by Paul Kelly about 8 years ago

  • Status changed from New to Assigned
  • Assignee set to Paul Kelly

#3 Updated by Paul Kelly about 8 years ago

rebased and tested

#4 Updated by Paul Kelly about 8 years ago

  • Status changed from Assigned to Ready For Testing

#5 Updated by Ohad Levy about 8 years ago

  • Target version set to 0.2

#6 Updated by Paul Kelly about 8 years ago

  • % Done changed from 0 to 100

#7 Updated by Ohad Levy about 8 years ago

  • Status changed from Ready For Testing to Closed

Also available in: Atom PDF