[Bug 985489] Re: nova-compute stops processing compute.$HOSTNAME occasionally on libvirt
** Summary changed: - nova-compute stops processing compute.$HOSTNAME occasionally + nova-compute stops processing compute.$HOSTNAME occasionally on libvirt -- 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/985489 Title: nova-compute stops processing compute.$HOSTNAME occasionally on libvirt To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/985489/+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 985489] Re: nova-compute stops processing compute.$HOSTNAME occasionally on libvirt
** Summary changed: - nova-compute stops processing compute.$HOSTNAME occasionally + nova-compute stops processing compute.$HOSTNAME occasionally on libvirt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/985489 Title: nova-compute stops processing compute.$HOSTNAME occasionally on libvirt To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/985489/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 838581] Re: Failures in db_pool code: 'NoneType' object has no attribute '_keymap' or not returning rows.
I know this is an old bug, but I'm pretty confident now that the problem isn't in db_pool, just that the increased concurrency exposed bugs in nova. This was complicated by bugs in SQLAlchemy (since fixed) and in MySQLdb (which I've opened up a bug report and supplied a patch) that masked the real bug in nova. The 'NoneType' object has no attribute '_keymap' exception is most likely caused by a bug in SQLAlchemy that has been fixed for a while. I was only able to reproduce this with older versions of SQLAlchemy, whereas upgrading to a recent version results in the ResourceClosedError: This result object does not return rows. It has been closed automatically. exception. The exception is generated by SQLAlchemy, but is ultimately a bug in MySQLdb, where it doesn't always raise an exception correctly when it is received by the server. For some reason, with subtle changes to the query, errors can happen at different points in the protocol and MySQLdb doesn't handle it correctly if the error is received when calling mysql_store_result(). I opened up this bug report and attached a patch to fix the bug in MySQLdb: https://sourceforge.net/tracker/?func=detailaid=3546166group_id=22307atid=374932 After upgrading SQLAlchemy and fixing MySQLdb, you'll see the real problem, which is likely this exception: OperationError: Deadlock found when trying to get lock; try restarting transaction At least that was the case with the quota reservation code, tracked by this bug: https://bugs.launchpad.net/nova/+bug/1026709 I strongly suspect these other cases are similar bugs with incorrect locking since at least the fixed_ip code uses with_lockmode as well. ** Bug watch added: SourceForge.net Tracker #3546166 http://sourceforge.net/support/tracker.php?aid=3546166 -- 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/838581 Title: Failures in db_pool code: 'NoneType' object has no attribute '_keymap' or not returning rows. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/838581/+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 838581] Re: Failures in db_pool code: 'NoneType' object has no attribute '_keymap' or not returning rows.
I know this is an old bug, but I'm pretty confident now that the problem isn't in db_pool, just that the increased concurrency exposed bugs in nova. This was complicated by bugs in SQLAlchemy (since fixed) and in MySQLdb (which I've opened up a bug report and supplied a patch) that masked the real bug in nova. The 'NoneType' object has no attribute '_keymap' exception is most likely caused by a bug in SQLAlchemy that has been fixed for a while. I was only able to reproduce this with older versions of SQLAlchemy, whereas upgrading to a recent version results in the ResourceClosedError: This result object does not return rows. It has been closed automatically. exception. The exception is generated by SQLAlchemy, but is ultimately a bug in MySQLdb, where it doesn't always raise an exception correctly when it is received by the server. For some reason, with subtle changes to the query, errors can happen at different points in the protocol and MySQLdb doesn't handle it correctly if the error is received when calling mysql_store_result(). I opened up this bug report and attached a patch to fix the bug in MySQLdb: https://sourceforge.net/tracker/?func=detailaid=3546166group_id=22307atid=374932 After upgrading SQLAlchemy and fixing MySQLdb, you'll see the real problem, which is likely this exception: OperationError: Deadlock found when trying to get lock; try restarting transaction At least that was the case with the quota reservation code, tracked by this bug: https://bugs.launchpad.net/nova/+bug/1026709 I strongly suspect these other cases are similar bugs with incorrect locking since at least the fixed_ip code uses with_lockmode as well. ** Bug watch added: SourceForge.net Tracker #3546166 http://sourceforge.net/support/tracker.php?aid=3546166 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/838581 Title: Failures in db_pool code: 'NoneType' object has no attribute '_keymap' or not returning rows. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/838581/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 948595] Re: Default api-paste.ini does not properly route metadata requests to /1.0
The reason why I ask is because I don't even see a 1.0 EC2 API doc anywhere. It's not listed here: http://aws.amazon.com/archives/Amazon-EC2 and the latest version isn't 1.0. All of the versions fit -mm-dd format so 1.0 seems like it's a mistake not supposed to be in the list. I'm not an expert on the EC2 API but to me it looks like the inclusion in the list is a mistake and not the absence in the paste config. -- 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/948595 Title: Default api-paste.ini does not properly route metadata requests to /1.0 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/948595/+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 948595] Re: Default api-paste.ini does not properly route metadata requests to /1.0
Ok, I missed that you testes EC2 itself and saw 1.0 on there -- 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/948595 Title: Default api-paste.ini does not properly route metadata requests to /1.0 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/948595/+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 948595] Re: Default api-paste.ini does not properly route metadata requests to /1.0
The reason why I ask is because I don't even see a 1.0 EC2 API doc anywhere. It's not listed here: http://aws.amazon.com/archives/Amazon-EC2 and the latest version isn't 1.0. All of the versions fit -mm-dd format so 1.0 seems like it's a mistake not supposed to be in the list. I'm not an expert on the EC2 API but to me it looks like the inclusion in the list is a mistake and not the absence in the paste config. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/948595 Title: Default api-paste.ini does not properly route metadata requests to /1.0 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/948595/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 948595] Re: Default api-paste.ini does not properly route metadata requests to /1.0
Ok, I missed that you testes EC2 itself and saw 1.0 on there -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/948595 Title: Default api-paste.ini does not properly route metadata requests to /1.0 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/948595/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 948595] Re: Default api-paste.ini does not properly route metadata requests to /1.0
Is the bug that 1.0 doesn't route anywhere or that 1.0 is in the list in the first place? I can't find any documentation on what a 1.0 API should 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/948595 Title: Default api-paste.ini does not properly route metadata requests to /1.0 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/948595/+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 948595] Re: Default api-paste.ini does not properly route metadata requests to /1.0
Is the bug that 1.0 doesn't route anywhere or that 1.0 is in the list in the first place? I can't find any documentation on what a 1.0 API should be. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/948595 Title: Default api-paste.ini does not properly route metadata requests to /1.0 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/948595/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 799008] Re: glance creates zero-length images in local file store on Ubuntu oneiric
FWIW, I ran into this same problem on Debian Squeeze and WebOb 0.9.8. I upgraded to WebOb 1.0.8 and it fixed the problem for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/799008 Title: glance creates zero-length images in local file store on Ubuntu oneiric To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/799008/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
