Skip to content

[master] Fix "Execution failed.: ( 1366: Incorrect integer value: 'None' for column 'RunNumber'"

Chris Burr requested to merge cburr/LHCbDIRAC:fix-trans-error into master 
2021-06-02 14:43:57 UTC Transformation/TransformationManager/Transformation/TransformationDB ERROR: _update (UPDATE TransformationFiles SET `RunNumber` = 'None',`FileType` = 'SIM',`Size` = '774578283'        WHERE TransformationID = 124020 AND FileID = 545846592): Execution failed. 1366
2021-06-02 14:43:57 UTC Transformation/TransformationManager ERROR: Failed to update TransformationFiles table MySQL Error ( 1131 : Execution failed.: ( 1366: Incorrect integer value: 'None' for column 'RunNumber' at row 1 ))
2021-06-02 14:43:57 UTC Transformation/TransformationManager NOTICE: Returning response ([2001:1458:d00:b::100:3e9]:51706)[hosts:lbvobox310.cern.ch] (0.02 secs) ERROR: MySQL Error ( 1131 : Execution failed.: ( 1366: Incorrect integer value: 'None' for column 'RunNumber' at row 1 ))

The issue is that setParameterToTransformationFiles is called in PluginUtils.getMetadataFromTSorBK with dictionaries like: {'/lhcb/MC/2018/SIM/00124019/0028/00124019_00289699_1.sim': {'RunNumber': None, 'FileType': 'SIM', 'Size': 727701221}}. The getMetadataFromTSorBK function only logs this in verbose output so the error is effectively silent.

I'm leaving this as a draft for now as I can't figure out why this has suddenly appeared but it has been hotfixed in production for the TransformationAgents. I've checked in the TransformationDB, TransformationManager, BookkeepingDB and PluginUtils but nothing seems to have changed with regard to handling RunNumber since before v10r1. Any ideas?

BEGINRELEASENOTES

*Transformation FIX: Fix "Execution failed.: ( 1366: Incorrect integer value: 'None' for column 'RunNumber'"

ENDRELEASENOTES

Edited by Chris Burr

Merge request reports