Open Stack

Check that both tables are set to the same collation (InnoDB, etc.)  Several of us have seen this same thing on foreign keys, and it’s because of a collation mismatch between the tables.





On 8/20/15, 9:25 AM, "Jonathan Proulx" <jon at jonproulx.com> wrote:

>H i All,
>
>I'm hitting a DB migration error while attempting a production upgrade
>(despite having successfully ruin the same upgrade on an only slightly
>older copy of the database last week)
>
>in:
>INFO  [alembic.migration] Running upgrade 38495dc99731 -> 4dbe243cd84d, nsxv
>
>Failing:
>sqlalchemy.exc.OperationalError: (OperationalError) (1005, "Can't
>create table 'csail_stata_neutron.nsxv_internal_networks' (errno:
>150)") "\nCREATE TABLE nsxv_internal_networks (\n\tnetwork_purpose
>ENUM('inter_edge_net') NOT NULL, \n\tnetwork_id VARCHAR(36),
>\n\tPRIMARY KEY (network_purpose), \n\tFOREIGN KEY(network_id)
>REFERENCES networks (id) ON DELETE CASCADE\n)ENGINE=InnoDB\n\n" ()
>
>poking by hand I can verify the FOREIGN KEY bit is what's failing but
>I definitely have a 'networks' table and it definitely has 'id' fields
>so not sure what is wrong here.
>
>My production control plane is currently off line so any suggestions
>would be much appreciated.
>
>-Jon
>
>_______________________________________________
>Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>Post to     : openstack at lists.openstack.org
>Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack