Expected Mysql version 4.0.0 does not match the latest schema 4.0.0-rc2n

Created by: Alexander Schlemmer

As of today I receive the following error message when starting the caosdb-server using caosdb-deploy with revision configuration: SERVER: dev PYLIB: dev MYSQLBACKEND: dev WEBUI: dev

linkahead        | 13:39:23.524 [main] ERROR org.caosdb.server.database.backend.implementation.MySQL.DatabaseConnectionPool - Version of the MySQL schema is wrong.
linkahead        | 	Expected: v4.0.0
linkahead        | 	Actual: v4.0.0-rc2n
linkahead        | Please upgrade the mysql backend.
linkahead        | 
linkahead        | 
sqldb_1          | 2021-02-11 13:39:23 54 [Warning] Aborted connection 54 to db: 'caosdb' user: 'caosdb' host: '172.20.0.3' (Got an error reading communication packets)
sqldb_1          | 2021-02-11 13:39:23 53 [Warning] Aborted connection 53 to db: 'caosdb' user: 'caosdb' host: '172.20.0.3' (Got an error reading communication packets)
sqldb_1          | 2021-02-11 13:39:23 52 [Warning] Aborted connection 52 to db: 'caosdb' user: 'caosdb' host: '172.20.0.3' (Got an error reading communication packets)
linkahead        | make: *** [Makefile:50: run-single] Error 1
linkahead        | CaosDB exited unsuccessfully.
linkahead exited with code 50

So specifically it complains about the mysql schema version expected by the server is not equal to the latest applied patch: Expected: v4.0.0 Actual: v4.0.0-rc2n

I checked, that on the mysqlbackend-side this is actually right:

linkahead        | applying patch ./patch20181119-2.1.0/patch.sh to caosdb ... [UPTODATE]
linkahead        | applying patch ./patch20190327-2.1.1/patch.sh to caosdb ... [UPTODATE]
linkahead        | applying patch ./patch20200420-2.1.2/patch.sh to caosdb ... [UPTODATE]
linkahead        | applying patch ./patch20200615-3.0.0rc1/patch.sh to caosdb ... [UPTODATE]
linkahead        | applying patch ./patch20200710-3.0.0-rc2/patch.sh to caosdb ... [UPTODATE]
linkahead        | applying patch ./patch20201110-4.0.0-rc1/patch.sh to caosdb ... [UPTODATE]
linkahead        | applying patch ./patch20201124-4.0.0-rc2/patch.sh to caosdb ... [UPTODATE]

My current workaround is to set the server version to: c9e63feb

Unfortunately @henrik_indiscale was not able to reproduce that problem. What can I do to narrow down the cause?

Imported comments:

By Timm Fitschen on 2021-02-11T19:57:16.548Z

The problem can be reproduced with a dump with that version (4.0.0-rc2). The bug is in caosdb-mysql and is my fault. The fix is in caosdb-mysqlbackend@9f5af78d

By Timm Fitschen on 2021-02-11T19:52:45.128Z

mentioned in commit caosdb-mysqlbackend@9f5af78d