Quesnelia (R1 2024) Required manual migrations

Owned by Pavlo Smahin
Last updated: Oct 09, 2024 by Julian Ladisch
2 min read

Module

Instructions

Comments

Contact person/
Automation Jira

Module

Instructions

Comments

Contact person/
Automation Jira

PostgreSQL

Migrate from PostgreSQL 12 to a more recent version by November 14, 2024.

PostgreSQL 12 will reach end of life (no security fixes!) on November 14, 2024.

FOLIO officially supports PostgreSQL 16 from Quesnelia on.

Quesnelia is the official PostgreSQL transition release that can run under both PostgreSQL 12 and PostgreSQL 16, this will allow deployed environments to transition. PostgreSQL 13, 14, and 15 are not officially supported but are in use in several institutions and are known to work with Poppy and Quesnelia. There are no known issues running Poppy with PostgreSQL 16.

@Julian Ladisch

mod-inventory-storage

Fixed since Quesnelia CSP#1 if there are less than 3 million holdings records.

Holdings records must be migrated

Important! The manual migration was included in module migrations. The instructions for manual script only apply if there are more than 3M affected holding records in the tenant database. If there are more affected records, then the manual script should be applied first and module should be enabled after script is done. (see the Instructions link)

@Pavlo Smahin

Partly fixed in mod-inventory-storage 27.1.4 released as Quesnelia CSP#1.

mod-circulation-storage

Fixed since Quesnelia CSP#2.

If library has changed any reference data ( https://github.com/folio-org/mod-circulation-storage/tree/v17.2.0/reference-data ) and migrates using loadReference = true: Make a backup before migration and restore afterwards.

Migration from Poppy to Quesnelia resets reference data.
Other modules don’t touch existing reference data when migrating with parameter loadReference = true, but mod-circulation-storage does.
Most notable reference data that gets reset to default: Circulation rules.

@Stephanie Buck

Fixed in mod-circulation-storage 17.2.3 released as Quesnelia CSP#2.

 

mod-data-export-spring

This manual task is only needed if at least one other tenant stays on Poppy. This manual task is not needed if all tenants are migrated to Quesnelia at the same time.

Before migrating a tenant from Poppy to Quesnelia run

UPDATE mod_data_export_spring_quartz.databasechangelog SET md5sum = '8:cd7cacfe2480c5305d1eaff157a35e4f' WHERE id = 'quartz-init'

After the migration run

UPDATE mod_data_export_spring_quartz.databasechangelog SET md5sum = '9:89aea1286f2c2901835da380fa17eff7' WHERE id = 'quartz-init'

 

Without the manual task the Poppy version of mod-data-export-spring fails and shuts down on start and restart with

Change failed validation!
Error creating bean with name 'quartzSchemaInitializer'
initial-schema.xml::quartz-init::quartz was: 9:89aea1286f2c2901835da380fa17eff7 but is now: 8:cd7cacfe2480c5305d1eaff157a35e4f

@Serhii_Nosko