yahoo-eng-team team mailing list archive

Thread
Date

[Bug 1201711] Re: Wrong unique key name in 200 migration

To: yahoo-eng-team@xxxxxxxxxxxxxxxxxxx
From: David Ripton <dripton@xxxxxxxxxx>
Date: Wed, 06 Nov 2013 06:00:29 -0000
Reply-to: Bug 1201711 <1201711@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

This fix got merged before the final Havana release, but the magic that
should have closed the bug failed.  (I think because of a stray period
after the bug number.)

** Changed in: nova
       Status: In Progress => 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/1201711

Title:
  Wrong unique key name in 200 migration

Status in OpenStack Compute (Nova):
  Fix Released

Bug description:
  In migration 200 this patch https://review.openstack.org/#/c/33127/19,
  was add unique constraint with bad name. Unfortunately this will work
  in sqlite and won't work in mysql and psql.

  So this code won't work properly in production databases.

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