-
Bug
-
Resolution: Unresolved
-
Blocker
-
1.34.0
-
None
-
False
-
None
-
False
-
-
When we have a DI or JS database initialized with the OSL 1.33.0, and we start same services re-using their respective databases with OSL 1.34.0, when any of them starts, errors like below are being produced.
(Note that the same will happen for Workflows databases)
Just one example below:
Caused by: org.flywaydb.core.api.exception.FlywayValidateException: Validate failed: Migrations have failed validation
Migration checksum mismatch for migration version 1.32.0
-> Applied to database : 1722286283
-> Resolved locally : -1617474746
Either revert the changes to the migration, or run repair to update the schema history.
:point_up: that error somehow says that for example the checksum for of the db script db/migration/V1.32.0_data_index_create.sql we had in OSL 1.33.0, differs from the checksum for the same DB script db/migration/V1.32.0_data_index_create.sql OSL 1.34.0
By doing an inspection of the content of these two files in the respective product branches.
[9.100.x-prod] (no license header)
https://github.com/kiegroup/kogito-apps/blob/eb16887d62aca443d84bee0c110ba1d471a9d[…]/src/main/resources/db/migration/V1.32.0__data_index_create.sql
[9.101.x-prod] (contains license header, braking change)
https://github.com/kiegroup/kogito-apps/blob/5010660ebeac85b211991c98763eef5630b45[…]/src/main/resources/db/migration/V1.32.0__data_index_create.sql
Basically from 9.100.x-prod branch, to 9.101.x-prod branch we introduced the license header in all the .sql files, and this produces a braking change. Not only in our product, but in community, etc.
- is depended on by
-
FLPATH-1787 [Tracking] M2 - sonata platform index and jobs service pods clbo "Migrations have failed validation"
- New