** No longer affects: keystone ** No longer affects: heat
** No longer affects: oslo-incubator ** No longer affects: cinder ** No longer affects: ceilometer ** No longer affects: nova -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1231657 Title: DB2 disconnect not handled pessimistically Status in OpenStack Image Registry and Delivery Service (Glance): In Progress Status in OpenStack Neutron (virtual network service): Triaged Bug description: Only MySQL server disconnect is being handled pessimistically by adding a pool checkout listener to the sqlalchemy engine. Since DB2 connection pool is not handled pessimistically, we get the following error after a temporarily disconnect of DB2 server that is already up and running: 2013-09-15 13:49:48.274 1013 TRACE nova.api.openstack OperationalError: (OperationalError) ibm_db_dbi::OperationalError: [IBM][CLI Driver] SQL30081N A communication error has been detected. Communication protocol being used: "TCP/IP". Communication API being used: "SOCKETS". Location where the error was detected: "172.17.35.52". Communication function detecting the error: "send". Protocol specific error code(s): "110", "*", "*". SQLSTATE=08001 SQLCODE=-30081 To avoid this error DB2 needs to be included in the logic to handle the connections pessimistically. To recreate in glance: Run glance index and make sure it is working Restart DB2 server Run glance index again, you will see error above. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1231657/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
