[Bug 1333630] Re: screen caught signal 11 core dumped

2014-10-27 Thread Jon Proulx
Any chance the fix will be back ported? broken screen in LTS is kinda
bad...

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to screen in Ubuntu.
https://bugs.launchpad.net/bugs/1333630

Title:
  screen caught signal 11 core dumped

To manage notifications about this bug go to:
https://bugs.launchpad.net/screen/+bug/1333630/+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


[Bug 1061166] Re: ec2 instance IDs are broken after folsom upgrade

2012-10-10 Thread Jon Proulx
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
instances.uuid=instance_id_mappings.uuid and
instance_id_mappings.idinstances.id;

seems to me instance_id_mappings only contains duplicated information
which can only lead ot suffering like this, guess I should go read the
code and revision history if I want to see how this came to be.

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


[Bug 1061166] Re: ec2 instance IDs are broken after folsom upgrade

2012-10-09 Thread Jon Proulx
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.py
and
/usr/local/nova/nova/db/sqlalchemy/api.py

then pycompiled  /usr/lib/python2.7/dist-
packages/nova/db/sqlalchemy/api.py (as there was an existing file of
that name), I've restated the api service and even rebooted the system
and still get the InstanceNotFound errors when attempting tho delete
(euca-terminate-instances) or assign floating ips (euca-associate-
address)

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


[Bug 1061166] Re: ec2 instance IDs are broken after folsom upgrade

2012-10-09 Thread Jon Proulx
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-0027flood-x26   flood-x26   
running 0   m1.tiny 2012-10-09T14:42:16.000Znova

euca-terminate-instances i-4fb6 
InstanceNotFound: Instance i-4fb6 could not be found.

nova show shows this as having UUID 3f5d9fbf-eb02-4531-bacd-90df69f1233a
and converting the ec2 id to decimal gives me ID 20406

mysql select * from instance_id_mappings where 
uuid='3f5d9fbf-eb02-4531-bacd-90df69f1233a' or id=20406 ;
+-+++-+---+--+
| created_at  | updated_at | deleted_at | deleted | id| uuid
 |
+-+++-+---+--+
| 2012-10-09 14:42:16 | NULL   | NULL   |   0 | 20406 | 
3f5d9fbf-eb02-4531-bacd-90df69f1233a |
+-+++-+---+--+
1 row in set (0.00 sec)

mysql select created_at,updated_at,deleted_at,id,uuid,hostname from instances 
where uuid='3f5d9fbf-eb02-4531-bacd-90df69f1233a' or id=20406 ;
+-+-++---+--+---+
| created_at  | updated_at  | deleted_at | id| uuid 
| hostname  |
+-+-++---+--+---+
| 2012-10-09 14:42:16 | 2012-10-09 14:42:47 | NULL   | 20297 | 
3f5d9fbf-eb02-4531-bacd-90df69f1233a | flood-x26 |
+-+-++---+--+---+
1 row in set (0.00 sec)

do I need to ensure  instance_id_mappings.id == instances.id?  thats' a
little ugly, but possible to fix up on my end.

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