Bug - Upgrade from 3.29.1 to 3.30.0

Forum - Installation
1

Hi, Having some problems upgrading the community edition 3.29.1 to 3.30.0. Followed the repository update and docker switch but it fails on this when starting:

eramba          |  == 20260519143000 ComplianceManagementSingleCustomFieldValuesDeduplicateMigration: migrating
eramba          | Class "CustomFields\Model\Table\CustomFieldsTable" not found
eramba          | Data migrations failed.
eramba          | Migration process failed.
eramba          | Initialisation process failed.

It then just loops around. Tested it on our database and on a clean 3.29.1 database and the same thing happens.

AI came up with this which might help further

Community 3.30.0 upgrade fails — data migration references CustomFieldsTable class absent from Community image; reproduced on clean data

Environment: Community, Docker (simple-install), upgrading 3.29.1 → 3.30.0 (image 3.30.0-19, also reproduced via 3.x tag).

Failure: Structural migrations complete successfully. Data migrations fail on 20260519143000_ComplianceManagementSingleCustomFieldValuesDeduplicateMigration with Class "CustomFields\Model\Table\CustomFieldsTable" not found. Container crash-loops; transaction rolls back.

Root cause evidence: The migration file contains use CustomFields\Model\Table\CustomFieldsTable; and references CustomFieldsTable::TYPE_* constants, but CustomFieldsTable.php does not exist anywhere in the Community image (find /var/www/eramba -name CustomFieldsTable.php returns nothing in both eramba:latest and eramba:3.x). Appears the migration depends on a CustomFields plugin class not shipped in the Community build.

Great product by the way, hoping to upgrade to Enterprise soon! Thanks

2

Hi,

I ran into a similar issue during the update as well, not with the loop but with the CustomFieldsTable. I was able to resolve it in the end by using the release-3.30.0 image instead of the 3.30.0-x image.

Might be worth a try in your case too.

1 Like
3

@Tom Thanks! Using the release-3.30.0 image worked

Thanks

1 Like
4

Thanks for reporting this. We’re already looking into it and I’ll let you know as soon as we have an update

1 Like