FAILING Data service status is reset to WORKING during DB patching
Assignee

Reporter

Labels
Sprint
None
Description
Steps to reproduce
None
was caused by
Activity
Show:

Dominik Janura October 16, 2020 at 7:27 AMEdited
Tested OK in 5.8.1.3

Tomas Horsky October 15, 2020 at 5:14 PM
Fixed in the original DB patch. Patch is now as it was meant to be in original commit for .
Upgrade to 5.8.0 will have this problem, but when DS is triggered, its state will go back to FAILING / WORKING as expected.
Upgrade directly to 5.8.1 should be without this problem.
Fixed
Details
Details
Priority
Fix versions
Affects versions
Branch
QA Testing
UNDECIDED
Components
Created October 15, 2020 at 8:12 AM
Updated September 12, 2023 at 8:44 AM
Resolved October 15, 2020 at 5:14 PM
During MySQL database patching to version 5.8.0 there is this command in 0140_move_health_configuration.sql
This resets the state of a FAILING data service to WORKING
Other DB dialects do not have the set state='WORKING' part in the patch file.
Expected behavior: Data service should keep its state during upgrade from 5.7.x to 5.8.x.