The method for calculating schema checksums makes it hard to reproduce this in standalone setup during migration. Additionally checksums are problematic in case of compatible versions of a manager, those versions could have slightly different checksums and we currently do not have a way to handle that. In general checksums are not so useful as we hoped, and for now the simplest way to avoid all problems is to avoid checking them altogether.
This ticket is to just suppress the check, but we still can keep checksum methods and checksums in the database for now, in case we discover we still want them. A follow-up ticket would be to clean up the code and database values from all checksums.