Bug 894917 - RFE: Support database row archiving/deletion [NEEDINFO]
Summary: RFE: Support database row archiving/deletion
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-nova
Version: 2.0 (Folsom)
Hardware: All
OS: Linux
Target Milestone: Upstream M1
: 4.0
Assignee: David Ripton
QA Contact: Brent Eagles
URL: https://blueprints.launchpad.net/nova...
Keywords: FutureFeature, OtherQA
Depends On: 960644 1221962
Blocks: RHOS40RFE
TreeView+ depends on / blocked
Reported: 2013-01-14 01:41 UTC by Perry Myers
Modified: 2015-05-15 10:46 UTC (History)
10 users (show)

Clone Of:
Last Closed: 2013-12-19 23:57:14 UTC
mlopes: needinfo? (dripton)

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2013:1859 normal SHIPPED_LIVE Red Hat Enterprise Linux OpenStack Platform Enhancement Advisory 2013-12-21 00:01:48 UTC

Description Perry Myers 2013-01-14 01:41:21 UTC
This tracks upstream blueprint: https://blueprints.launchpad.net/nova/+spec/db-archiving

Comment 1 David Ripton 2013-02-18 18:47:52 UTC
The upstream development work is done for this blueprint; it will be in Grizzly final.

Comment 4 David Ripton 2013-03-05 16:22:27 UTC
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.

Comment 5 David Ripton 2013-03-26 15:19:14 UTC
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.

Comment 6 David Ripton 2013-04-24 18:45:08 UTC
Setting to POST because these commits are already in upstream Grizzly and will naturally get into 3.0.

Comment 12 errata-xmlrpc 2013-12-19 23:57:14 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.