Bug #566

Pool Objects reuse deleted ids

Added by Carlos Martín almost 10 years ago. Updated over 9 years ago.

Status:ClosedStart date:04/08/2011
Priority:NormalDue date:
Assignee:Carlos Martín% Done:


Category:Core & System
Target version:Release 3.0
Resolution:fixed Pull request:
Affected Versions:


All Pool Objects have a unique ID called oid. This oid is auto-incremented from the last one found in the pool tables at star-up, and this can lead to re-usage of deleted IDs.

Example: Having a Pool with oids 1..7; if the last objects 5, 6 & 7 are deleted and OpenNebula re-started, the last oid found will be 4 and new oids will start from 5 (instead of from 8).

Associated revisions

Revision 691c9653
Added by Carlos Martín over 9 years ago

Bug #566: New control table to store the last used oid
Feature #591: Add new control table, and fix SQL syntax for MySQL

Revision 49058dd4
Added by Abel Coronado about 3 years ago

F #5241: Merged vCenter and KVM views (#566)

Revision b9b272f0
Added by Ruben S. Montero about 3 years ago

Revert "F #5241: Merged vCenter and KVM views (#566)"

This reverts commit 49058dd4ab84dfa4fcbf7938c1ddb3e09e2a607f.


#1 Updated by Carlos Martín over 9 years ago

This issue will be solved in branch feature-591

#2 Updated by Ruben S. Montero over 9 years ago

  • Status changed from New to Closed
  • Resolution set to fixed

The changes are now in master

Also available in: Atom PDF