Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Current »

Date

Authors

Andy Dingley

Status

Documenting

Summary

NIMDTA reference service could not start

Impact

TIS NIMDTA unavailable

Non-technical Description

The reference service for NIMDTA was stuck in a cycle attempting to step in our database migration tool. A database configuration value was set incorrectly for the migration to be completed as expected.


Trigger

  • OrganizationType reference type deployed to production with Flyway script to create required database table and trigger.


Detection

  • Notification sent to #monitoring-prod.


Resolution

  • Set the global variable log_bin_trust_function_creators to ON in the NIMDTA production database.

  • Delete the OrganizationType table to avoid issues from the partial update.

  • Delete the failed migration from the schema history table.

  • Let the reference service restart and run the migration again with the correct access.



Timeline

  • : 12:20 BST - New flyway migration deployed to production

  • : 12:23 BST - Notification in #monitoring-prod.

  • : 12:42 BST - Call started in #tis-dev-team

  • : 12:43 BST - Fix deployed.

Root Cause(s)

  • Flyway migration validation failed due to a lack of permissions to create a trigger.

  • Global variable log_bin_trust_function_creators on NIMDTA production database was set to OFF instead of ON

  • A MySQL restart on 2021-05-13 reset this to the defaulted value OFF and it is not clear whether this was manually changed


Action Items

Action Items

Owner

Ensure any restart/automated process (ansible) sets log_bin_trust_function_creators correctly

Joseph (Pepe) Kelly

Document how to investigate Flyway migration issues.

Andy Dingley


Lessons Learned

  • No labels

0 Comments

You are not logged in. Any changes you make will be marked as anonymous. You may want to Log In if you already have an account.