I upgraded today and found that I had this issue.
Not all of my instances had duplicate entries in the
`instance_id_mappings` table, however I did have more entries within the
`instance_id_mappings` than within the `instances` table.
It seems that the `id` column in the `instances` table is still being
used somewhere.
In order to work around the problem I needed to set the auto_increment
integer to be the same for each table.
Example:
-- grab the auto_increment integer for `instances` table
SELECT Auto_increment FROM information_schema.tables WHERE
table_name='instances' AND table_schema='nova';
-- grab the auto_increment integer for `instances` table
SELECT Auto_increment FROM information_schema.tables WHERE
table_name='instance_id_mappings' AND table_schema='nova';
-- raise the lowest number returned to the same as the highest for the
relevant table.
ALTER TABLE instances AUTO_INCREMENT = 1769801923;
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1061166
Title:
ec2 instance IDs are broken after folsom upgrade
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1061166/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
