airajena commented on PR #5566: URL: https://github.com/apache/fineract/pull/5566#issuecomment-4009713713
> rebased on `develop` again. 🤷 I investigated the MariaDB 12 CI failures after rebasing to latest develop. The `Access denied for user 'runner'` line is not the root cause. It comes from the readiness probe using `mysqladmin ping` without credentials, but the workflow continues immediately into DB initialization, so that warning is just noise. The actual failures happen later inside the integration tests, after MariaDB and Fineract are already up. The common error is: `Record has changed since last read` I found this in the failing shards for: - `FeignTrialBalanceSummaryReportTest.testExternalAssetOwnerEntriesAppearInReport` - `ExternalAssetOwnerTransferCancelTest` - `InitiateExternalAssetOwnerTransferTest.saleTransferWithSameOwnerExternalIdInParallelShouldNotFail` - `SavingsAccountTransactionTest.testDeadlockSavingsBatchTransactions` - `SavingsAccountTransactionTest.testConcurrentSavingsBatchTransactions` The affected tables are: - `m_external_asset_owner_transfer` - `m_savings_account` This points to a MariaDB 12 transaction-behavior change, not a JDBC auth/handshake problem and not a Liquibase/Hibernate startup issue. The failure is concentrated in concurrency-sensitive write paths, and I was able to reproduce and validate locally against `mariadb:12.2`. The fix was to explicitly disable `innodb_snapshot_isolation` for MariaDB 12 startup paths. After setting `innodb_snapshot_isolation=OFF`, the previously failing targeted tests passed locally on MariaDB 12.2. I applied that consistently in: - GitHub Actions MariaDB workflow - local Docker compose - Kubernetes MariaDB deployment - MariaDB Testcontainers setup in `CommandBaseTest` I also updated the readiness probe to use root credentials so the logs no longer show the misleading `runner` access-denied message. So the issue was not the healthcheck warning; the real regression was MariaDB 12 snapshot isolation causing `Record has changed since last read` failures in Fineract’s concurrent integration test scenarios. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
