Description of problem: On table recipe_task_result column recipe_task_id is nullable it should be nullable=False to avoid orphaned data. As part of the migration script deletion of potential orphans should be done.
On a recent production snapshot: MySQL [beaker_dcallagh]> select count(*) from recipe_task_result where recipe_task_id is null; +----------+ | count(*) | +----------+ | 0 | +----------+ 1 row in set (0.01 sec) This one will be a *very* costly migration, there are ~120 million recipe_task_result rows in our production db.
https://gerrit.beaker-project.org/5963
There is no expected change in behaviour here, so verification should just be that the database migration succeeds (it did) and that nothing else breaks.
Beaker 25.0 has been released. Release notes are available upstream: https://beaker-project.org/docs/whats-new/release-25.html