Feature #5449
openImprovement of kb-recalc script
0%
Description
Right now it is possible to "delete" a pair <KB record, Error trace> by modifying KB record fields module, rule, main or script because of current implementation of kb-recalc script.
In LDV Analytics Center 0.11 it may lead to lose of already published KB records (corresponding Bug on linuxtesting.org will have a link to LDV Analytics Center with published trace but without published KB record).
Possible temporarily solution: create a new KB record that was deleted, manually set corresponding field published_trace_id in table results_kb to corresponding Bug id on linuxtesting.org (~ "UPDATE results_kb SET published_trace_id=<corresponding_bug_id> WHERE trace_id=<corresponding_trace_id> AND kb_id=<corresponding_kb_id>;") and then use "Update" button. Also in LDV Analytics Center 0.11 it is possible to find all those "deleted" KB records (which is not attached to any error trace) on page "Knowledge base" and delete them.
Updated by Evgeny Novikov almost 10 years ago
- Status changed from New to Open
- One for LDV Uploader that will try to match existing KB records with a newly uploaded error traces (so we will avoid the need to wait while verification results will be uploaded in one transaction prior to match KB records). Besides LDV Uploader should allow to re-invoke KB Recalc on already uploaded error traces.
- One for LDV Analytics Center that will (re)match new (updated/deleted) KB records with existing error traces and in particular will implement the requested feature. Besides LDV Analytics Center should allow to add new KB records from a user file (e.g. stored somewhere else) and recalculate the whole cache if something went wrong or uncommon scenarios, e.g. manipulating KB records from MySQL console, were used (in the administration mode).