- Release notes
Integration Service release notes
2.2510.1
Release date: December 19, 2025
General fixes
This release brings security updates and patches to address Common Vulnerabilities and Exposures (CVEs).
Known issue
Erratum - Added April 8, 2026: This issue was initially incorrectly documented as fixed in this release. The issue will be fixed in release 2.2510.2.
Integration Service pods fail to come up due to database change locks
In rare cases, especially during installation or upgrade, some Integration Service pods such as intsvcs-udon-api, intsvcs-udon-dbdeploy, intsvcs-periodic-dbdeploy, or intsvcs-ezra-dbdeploy may fail to come up and the following error is logged:
2025-10-27T11:43:15Z ERROR: Exception Primary Source: 4.31.1
2025-10-27T11:43:15Z ERROR: Exception Details
2025-10-27T11:43:15Z ERROR: Exception Primary Class: LockException
2025-10-27T11:43:15Z ERROR: Exception Primary Reason: Could not acquire change log lock. Currently locked by intsvcs-udon-dbdeploy-w7dpm (10.42.0.210) since 10/27/25, 11:38 AM
2025-10-27T11:43:15Z ERROR: Exception Primary Source: 4.31.1
2025-10-27T11:43:15Z Unexpected error running Liquibase: Could not acquire change log lock. Currently locked by intsvcs-udon-dbdeploy-w7dpm (10.42.0.210) since 10/27/25, 11:38 AM
2025-10-27T11:43:15Z ERROR: Exception Primary Source: 4.31.1
2025-10-27T11:43:15Z ERROR: Exception Details
2025-10-27T11:43:15Z ERROR: Exception Primary Class: LockException
2025-10-27T11:43:15Z ERROR: Exception Primary Reason: Could not acquire change log lock. Currently locked by intsvcs-udon-dbdeploy-w7dpm (10.42.0.210) since 10/27/25, 11:38 AM
2025-10-27T11:43:15Z ERROR: Exception Primary Source: 4.31.1
2025-10-27T11:43:15Z Unexpected error running Liquibase: Could not acquire change log lock. Currently locked by intsvcs-udon-dbdeploy-w7dpm (10.42.0.210) since 10/27/25, 11:38 AM
This occurs when a previous container exited unexpectedly without properly releasing the acquired database change locks, causing subsequent retries to fail.
If this issue occurs, follow these steps to fix it:
- Get the SQL connection string for the cluster.
- Navigate to the
IS_AutomationSuitedatabase. - Navigate to the
DATABASECHANGELOGLOCKtable of the affected service. For example, the tables forudon,periodic, andezraare
is_udon.DATABASECHANGELOGLOCK, is_periodic.DATABASECHANGELOGLOCK, and is_ezra.DATABASECHANGELOGLOCK respectively.
4. This table should contain a single entry with LOCKED = 1. Delete this row.
5. When the pod tries to come up again as part of a retry or when you resync the Integration Service app, it should start as expected.