Bug 1393186

Summary: Database Integrity Scheduler recipe_task_result
Product: [Retired] Beaker Reporter: Tyrone Abdy <tabdy>
Component: generalAssignee: Dan Callaghan <dcallagh>
Status: CLOSED CURRENTRELEASE QA Contact: tools-bugs <tools-bugs>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: developCC: dcallagh, mjia, rjoost
Target Milestone: 25.0Keywords: Patch
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-03-19 04:18:49 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Tyrone Abdy 2016-11-09 04:18:24 UTC 
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.
Comment 1 Dan Callaghan 2017-12-20 06:29:47 UTC 
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.
Comment 2 Dan Callaghan 2017-12-20 06:51:11 UTC 
https://gerrit.beaker-project.org/5963
Comment 4 Dan Callaghan 2018-01-10 03:28:33 UTC 
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.
Comment 6 Roman Joost 2018-03-19 04:18:49 UTC 
Beaker 25.0 has been released.

Release notes are available upstream: https://beaker-project.org/docs/whats-new/release-25.html