yahoo-eng-team team mailing list archive

[OpenStack Infra <1544349@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/278796
Committed: https://git.openstack.org/cgit/openstack/neutron-vpnaas/commit/?id=f4babb050ba5a54c9c9f91e2d1ac370539dadf3c
Submitter: Jenkins
Branch:    master

commit f4babb050ba5a54c9c9f91e2d1ac370539dadf3c
Author: ajmiller <al.miller@xxxxxxxxxxxx>
Date:   Wed Feb 10 15:34:34 2016 -0800

    Remove Foreign Key constraint during ALTER
    
    Beginning with MySQL 5.6, ALTER will fail if there are foreign key
    constraints affecting the column being altered.  This patch
    removes the constraint, before applying the update and then
    restores the constraint.
    
    Change-Id: I0982ec34d51f9e8004d85512bc8e0cde7b84b4f2
    Depends-On: Id3f199d688d648f4618a6850d094e26ca6bb9a7f
    Closes-Bug: 1544349


** Changed in: neutron
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1544349

Title:
  neutron-vpnaas db migration breaks in MySQL 5.6

Status in neutron:
  Fix Released

Bug description:
  Starting in MySQL 5.6, it is illegal to alter a column that is subject
  to a Foreign Key constraint, and any migration doing such will fail.
  Other projects (I have found examples in Barbican and Trove) work
  around this by removing the constraint, performing the ALTER, and
  reinstating the constraint.

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