** Changed in: nova
Milestone: grizzly-1 => 2013.1
--
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 notific
** Tags removed: 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
** Changed in: nova/folsom
Status: Fix Committed => Fix Released
--
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
** Changed in: nova
Status: Fix Committed => Fix Released
** Changed in: nova
Milestone: None => grizzly-1
--
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
** Changed in: nova/folsom
Milestone: None => 2012.2.1
--
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 not
** Branch linked: lp:~openstack-ubuntu-testing/nova/raring-grizzly
--
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 ma
** Changed in: nova/folsom
Assignee: (unassigned) => Adam Gandelman (gandelman-a)
--
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 f
** Branch linked: lp:~openstack-ubuntu-testing/nova/precise-folsom-
proposed
--
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 upgr
To answer my previous question for posterity, yes after removing
duplicates and resetting the auto incremnt as described above and
mismatch between the ids in instances and instance_id_mappings must be
recitified:
UPDATE instance_id_mappings,instances SET
instance_id_mappings.id=instances.id WHERE
** Also affects: nova/folsom
Importance: Undecided
Status: New
** Changed in: nova/folsom
Status: New => Fix Committed
** Changed in: nova/folsom
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
** Branch linked: lp:~openstack-ubuntu-testing/nova/quantal-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 ma
Reviewed: https://review.openstack.org/14240
Committed:
http://github.com/openstack/nova/commit/b7e509af5d8bc3f9e26dea5cf5121c0f62348dc0
Submitter: Jenkins
Branch:stable/folsom
commit b7e509af5d8bc3f9e26dea5cf5121c0f62348dc0
Author: Adam Gandelman
Date: Thu Oct 4 14:10:32 2012 -0700
** Branch linked: lp:ubuntu/nova
--
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
This bug was fixed in the package nova - 2012.2-0ubuntu4
---
nova (2012.2-0ubuntu4) quantal; urgency=low
* debian/patches/ubuntu/ubuntu-fix-ec2-instance-id-mappings.patch:
Backport from trunk, Set read_deleted='yes' for instance_id_mappings.
(LP: #1061166)
-- Chuck Short
I see that for instances that were running during the upgrade, but I'm
getting this error with new instances that do not have duplicate
entries:
euca-describe-instances i-4fb6
RESERVATION r-ttje080y 98333a1a28e746fa8c629c83a818ad57open
INSTANCEi-4fb6 ami-0
Jon-
Unfortunately if you've hit this bug, your instance_id_mappings table is
already polluted with duplicate entries and the mapping between EC2 IDs
and UUIDs is skewed.Someone may know a better work around, but in
the meantime I'd take a look at the instance_id_mappings table and clean
it of
This doesn't seem to be working for me, perhaps I implemented it
incorrectly, or need to take further remedial action?
(using ubuntu 12.04 coud archive version of nova-api as a base)
copied the patched verion of nova/db/sqlalchemy/api.py to
/usr/lib/python2.7/dist-packages/nova/db/sqlalchemy/api
Reviewed: https://review.openstack.org/14063
Committed:
http://github.com/openstack/nova/commit/1d0402cf65458c941639f01334a996c11e592018
Submitter: Jenkins
Branch:master
commit 1d0402cf65458c941639f01334a996c11e592018
Author: Adam Gandelman
Date: Thu Oct 4 14:10:32 2012 -0700
Set rea
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nova (Ubuntu)
Status: New => Confirmed
--
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
** Changed in: nova
Importance: Undecided => Critical
--
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 notif
The loose relationship between two auto_incrementing `id` columns of
different tables is insanely brittle. I am not convinced that the
intention was for the relation to work this way. It may simple be a
problem with part of the code referencing `id` instead of `uuid`.
The uuid's in the `instances_
Fix proposed to branch: master
Review: https://review.openstack.org/14063
** Changed in: nova
Status: New => In Progress
** Changed in: nova
Assignee: (unassigned) => Adam Gandelman (gandelman-a)
--
You received this bug notification because you are a member of Ubuntu
Server Team, w
>From what I can gather the 107 migration only copies the instance's ID
and UUID to the new mapping table, but leaves the other columns NULL,
specifically 'deleted'.
In Folsom, an ec2 describe instances call will check that the
instances.id <-> uuid mapping exists in the instances_id_mapping table
It looks like the id column should have been set to auto-increment after
the data copy was done
--
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 broke
This looks like a broken migration to me, based on the above comment:
https://github.com/openstack/nova/blob/master/nova/db/sqlalchemy/migrate_repo/versions/107_add_instance_id_mappings.py
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed t
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
** Tags added: ec2
--
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:/
Oops: should have read that instances i-0003 and i-0004 changed
post-upgrade to i-0005 and i-0006
--
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 in
After taking another look at this, EC2 instance IDs appear to change
during an upgrade.
Did an upgrade with two running instances, i-0003 and i-0004.
After upgrade, they show change to i-0003 and i-0004,
respecively. Any EC2 action (terminate, get-console-output, etc) on
these n
** Changed in: nova (Ubuntu)
Importance: Undecided => High
--
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
30 matches
Mail list logo
