testUpgradeInstanceWithOldDataFs: update dump using erp5-catalog-0 in connection string
This dump was made with a connection string on 127.0.0.1, which must be
causing erros in logs:
2020-04-09 09:35:02.699 CRITICAL ERP5Site Automatic migration of core tools failed
Traceback (most recent call last):
File "erp5/product/ERP5Type/dynamic/portal_type_class.py", line 456, in synchronizeDynamicModules
portal.portal_activities.initialize()
File "erp5/product/CMFActivity/ActivityTool.py", line 694, in initialize
activity.initialize(self, clear=False)
File "erp5/product/CMFActivity/Activity/SQLBase.py", line 173, in initialize
db = activity_tool.getSQLConnection()
File "erp5/product/CMFActivity/ActivityTool.py", line 674, in getSQLConnection
return self.aq_inner.aq_parent.cmf_activity_sql_connection()
File "eggs/Products.ZSQLMethods-2.13.5-py2.7.egg/Shared/DC/ZRDB/Connection.py", line 194, in __call__
self.connect(s)
File "erp5/product/ERP5Type/tests/ERP5TypeTestCase.py", line 926, in connect
return original_ZMySQLDA_connect(self, *args, **kw)
File "erp5/product/ZMySQLDA/DA.py", line 156, in connect
connection = pool[self._p_jar] = DB(s)
File "erp5/product/ZMySQLDA/db.py", line 229, in __init__
self._forceReconnection()
File "erp5/product/ZMySQLDA/db.py", line 316, in _forceReconnection
self.db = MySQLdb.connect(**self._kw_args)
File "develop-eggs/mysqlclient-1.3.12-py2.7-linux-x86_64.egg/MySQLdb/__init__.py", line 86, in Connect
return Connection(*args, **kwargs)
File "develop-eggs/mysqlclient-1.3.12-py2.7-linux-x86_64.egg/MySQLdb/connections.py", line 204, in __init__
super(Connection, self).__init__(*args, **kwargs2)
OperationalError: (2002, "Can't connect to MySQL server on '127.0.0.1' (115)")
Showing
No preview for this file type
This source diff could not be displayed because it is too large. You can view the blob instead.
-
Owner@arnau I'm trying this...
we don't see it here, but there's also:
index b8f92f0..52786c0 100644 --- a/test_data/testUpgradeInstanceWithOldDataFs/dump.sql +++ b/test_data/testUpgradeInstanceWithOldDataFs/dump.sql @@ -1,7 +1,13 @@ +-- MySQL dump 10.17 Distrib 10.3.18-MariaDB, for Linux (x86_64) +-- +-- Host: erp5-catalog-0 Database: erp5_test_0 +-- ------------------------------------------------------ +-- Server version 10.3.18-MariaDB-log + /*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT */; /*!40101 SET @OLD_CHARACTER_SET_RESULTS=@@CHARACTER_SET_RESULTS */; /*!40101 SET @OLD_COLLATION_CONNECTION=@@COLLATION_CONNECTION */; -/*!40101 SET NAMES utf8 */; +/*!40101 SET NAMES utf8mb4 */;because I used a mariadb more recent than slapos@dd8fee69
-
Owner
I'm trying something else. I think it would be better if we could make a
Data.fswith a connection string likeCONNECTION_STRING_BUT_SOMETHING_LONG_ENOUGHand at the beginning of the test open the Data.fs as a binary file and replaceCONNECTION_STRING_BUT_SOMETHING_LONG_ENOUGHwith the connection string that this test node is actually using.What I'm thinking is if we have a dump with a valid connection string, but used by another node of this testnode, then this will make this node connect to the database used by another node running another test.
I have a testnode installed locally, we can try this.
Please register or sign in to comment