db-archiving fails to clear some deleted rows from instances table
Bug #1183523 reported by
David Ripton
This bug affects 16 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Medium
|
Cédric LECOMTE | ||
Mitaka |
Fix Released
|
Medium
|
Matt Riedemann |
Bug Description
Downstream bug report from Red Hat Bugzilla against Grizzly: https:/
In unit tests, db-archiving moves all 'deleted' rows to the shadow tables. However, in the real-world test, some deleted rows got stuck in the instances table.
I suspect a bug in the way we deal with foreign key constraints.
Changed in nova: | |
assignee: | nobody → David Ripton (dripton) |
tags: | added: db |
Changed in nova: | |
importance: | Undecided → Medium |
status: | New → Confirmed |
Changed in nova: | |
status: | In Progress → Fix Committed |
To post a comment you must log in.
I ran into the same bug. It is because instance's uuid was used in some other tables as foreign key.
Not sure if it is caused by an inconsistent database.