[Bug 1061166] Re: ec2 instance IDs are broken after folsom upgrade
OpenStack Hudson
1061166 at bugs.launchpad.net
Tue Oct 9 20:44:23 UTC 2012
Reviewed: https://review.openstack.org/14240
Committed: http://github.com/openstack/nova/commit/b7e509af5d8bc3f9e26dea5cf5121c0f62348dc0
Submitter: Jenkins
Branch: stable/folsom
commit b7e509af5d8bc3f9e26dea5cf5121c0f62348dc0
Author: Adam Gandelman <adam.gandelman at canonical.com>
Date: Thu Oct 4 14:10:32 2012 -0700
Set read_deleted='yes' for instance_id_mappings.
Since the migration that creates the instance_id_mappings does
not populated the 'deleted' column, queries to this table should
not limit results to 'deleted=0'. Limiting to non-deleted rows
results in duplicate mappings being created for existing instance
mappings after an upgrade, and throws off the entire EC2 instance
ID to UUID mapping.
Fixes LP: #1061166
Change-Id: I8893954fcae94a71dcc284c1b3b23b53901437eb
(cherry picked from commit 1d0402cf65458c941639f01334a996c11e592018)
** Tags added: in-stable-folsom
--
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
More information about the Ubuntu-server-bugs
mailing list