This tracks upstream blueprint: https://blueprints.launchpad.net/nova/+spec/db-archiving
The upstream development work is done for this blueprint; it will be in Grizzly final.
There's an upstream bug related to this: https://bugs.launchpad.net/nova/+bug/1137977 Foreign keys mess up archiving. I need to fix this by Grizzly final.
Fixed the upstream bug https://bugs.launchpad.net/nova/+bug/1137977 in upstream commit bb1977718d697565d
They found another RHEL-only test failure bug https://bugs.launchpad.net/nova/+bug/1158828 It appears to be a problem with SQLAlchemy not reliably supporting SQLite foreign key constraints with the old version of SQLite that comes with RHEL 6.4 My upstream fix for that was to just skip the offending unit test if SQLite < 3.7 was detected. Upstream commit c07ec51dba9b1
The backport needs to also include those two commits.
Setting to POST because these commits are already in upstream Grizzly and will naturally get into 3.0.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.