Public bug reported:

After upgrading a running cluster from Essex to Folsom
(2012.2-0ubuntu2~cloud0), the EC2 API can no longer find instances by
EC2 ID, ie:

ubuntu@ip-10-252-38-15:~$ euca-describe-instances 
RESERVATION     r-90qer9xs      7b58c0e219a948ef942071c871d05b8b        default
INSTANCE        i-00000006      ami-00000001    192.168.25.4    192.168.25.4    
running adam (7b58c0e219a948ef942071c871d05b8b, ip-10-252-40-134)       0       
        m1.tiny 2012-10-03T18:35:03.000Z        novamonitoring-disabled 
192.168.25.4    192.168.25.4                    instance-store                  
                                                
RESERVATION     r-k190bhzm      7b58c0e219a948ef942071c871d05b8b        default
INSTANCE        i-00000004      ami-00000001    192.168.25.5    192.168.25.5    
running adam (7b58c0e219a948ef942071c871d05b8b, ip-10-252-40-134)       0       
        m1.tiny 2012-10-03T18:22:49.000Z        novamonitoring-disabled 
192.168.25.5    192.168.25.5                    instance-store                  
                                                
ubuntu@ip-10-252-38-15:~$ euca-get-console-output i-00000004
InstanceNotFound: Instance i-00000004 could not be found.

A quick test of other calls shows that this affects many actions:

euca-get-console-output
euca-terminate-instance
euca-attach-volumes
euca-associate-address

Should note that describing individual instances still works (ie, euca-
describe-instances i-00000004) still works as expected.  A quick glance
at the code shows this call converts the EC2 instance ID to UUID with
ec2utils.ec2_inst_id_to_uuid() rather than ec2utils.ec2_id_to_id() like
the other calls.

This seems to not affect clusters that have been initially installed
with Folsom.  I suspect something is wrong in the data migration from
Essex to Folsom that causes the ec2_id_to_id() mapping to be bogus.

** Affects: nova
     Importance: Undecided
         Status: New

** Affects: nova (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: openstack-ubuntu-upgrade

** Also affects: nova
   Importance: Undecided
       Status: New

** Tags added: openstack-ubuntu-upgrade

-- 
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

Reply via email to