yahoo-eng-team team mailing list archive

["Markus Zoeller \(markus_z\)" <mzoeller@xxxxxxxxxxxxxxxxxx>]

As we use the "direct-release" model in Nova we don't use the
"Fix Comitted" status for merged bug fixes anymore. I'm setting
this manually to "Fix Released" to be consistent.

[1] "[openstack-dev] [release][all] bugs will now close automatically
    when patches merge"; Doug Hellmann; 2015-12-07;
    http://lists.openstack.org/pipermail/openstack-dev/2015-December/081612.html


** Changed in: nova
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1183523

Title:
  db-archiving fails to clear some deleted rows from instances table

Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  Downstream bug report from Red Hat Bugzilla against Grizzly:
  https://bugzilla.redhat.com/show_bug.cgi?id=960644

  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1183523/+subscriptions