On 10/19/2016 9:47 AM, Carter, Kevin wrote:
Hi Matt and thanks for the reply,
We do have that commit as found here: [
https://github.com/openstack/nova/blob/dd30603f91e6fd3d1a4db452f20a51ba8820e1f4/nova/db/sqlalchemy/api.py#L1846
]. If there's anything you'd like to see as we're trying to figure
Hi Matt and thanks for the reply,
We do have that commit as found here: [
https://github.com/openstack/nova/blob/dd30603f91e6fd3d1a4db452f20a51ba8820e1f4/nova/db/sqlalchemy/api.py#L1846
]. If there's anything you'd like to see as we're trying to figure
this out I'd be happy to provide {any,every}t
On 10/19/2016 08:36 AM, Ian Cordasco wrote:
Hey Kevin,
So just looking at the pastes you have here, I'm inclined to believe
this is actually a bug in oslo_db/sqlalchemy. If you follow the trace,
there's a PyMySQL InternalError not being handled inside of
sqlalchemy. I'm not sure if SQLAlchemy
-Original Message-
From: Carter, Kevin
Reply: OpenStack Development Mailing List (not for usage questions)
Date: October 18, 2016 at 21:18:13
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [nova][oslo][openstack-ansible] DB
deadlocks, Mitaka
On 10/18/2016 9:16 PM, Carter, Kevin wrote:
Hello all,
As some folks may know the OSIC cloud1 just upgraded to Mitaka last
week (I know what's old is new again, sorry). Since the upgrade things
have been running fairly smoothly however there's been one issue that
has left me scratching my head.
Hello all,
As some folks may know the OSIC cloud1 just upgraded to Mitaka last
week (I know what's old is new again, sorry). Since the upgrade things
have been running fairly smoothly however there's been one issue that
has left me scratching my head. When attempting a scale out test we've
run int
