We've experienced some problems in a newer instance of our autotest server, when we discovered that one exception handling in the django db code (introduced by ee3cced1afb6bc45216c7038472827ad4033c3f5) had the wrong namespace for the DatabaseError. Without the appropriate path, the exception handling would itself throw a NameError exception, making the function return None.
This is expected to fix errors like: [Tue Jul 10 10:35:04 2012] [error] [client 1.2.3.4] return self.connection.rollback(), referer: http://foo.com/afe [Tue Jul 10 10:35:04 2012] [error] [client 1.2.3.4] OperationalError: (2006, 'MySQL server has gone away'), referer: http://foo.com/afe/ Signed-off-by: Lucas Meneghel Rodrigues <l...@redhat.com> --- frontend/db/backends/afe/base.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/frontend/db/backends/afe/base.py b/frontend/db/backends/afe/base.py index 8a0ff76..91f39cd 100644 --- a/frontend/db/backends/afe/base.py +++ b/frontend/db/backends/afe/base.py @@ -30,7 +30,7 @@ class DatabaseWrapper(MySQLDatabaseWrapper): try: self.connection.ping() return True - except DatabaseError: + except Database.DatabaseError: self.connection.close() self.connection = None return False -- 1.7.10.4 _______________________________________________ Autotest mailing list Autotest@test.kernel.org http://test.kernel.org/cgi-bin/mailman/listinfo/autotest
