Bug #5389
Updated by Nicolas CHARLES about 9 years ago
If we use, in different techniques generated by ncf-builder, the same components with the same values, thenthe reporting cannot distringuih which reports should match which technique, and we get "unknown" and "no answer" states The Techniques generated by ncf-builder have Using a unique name, Directive based on a metaTechnique which is also use the bundle name Rudder generates a csv file for reporting, in methods service_ensure_running and service_ensure_running_at_boot on the format <pre> technique_name;;class_prefix_${key};;@@RUDDER_ID@@;;component name;;component key </pre> So far, we used only the class_prefix_${key} as a key to extract data from the this csv file, to get the line to report. Problem: we may have several time the same class_prefix_${key}, if we use in different technique the same component with same value. Since we know the technique_name (we are calling it in the bundlesequence), we can use it in the key to search the csv file However, we don't want to pass the technique name down the chain of generic method, as it would service will be clunky, so we inject it in the bundle current_technique_report_info, by calling this bundle with the current ncf technique name And then, we change the logger_rudder to retrieve this value and expose the proper report line "Unknown" state. This ticket part is probably related to change the bundlesequence, to call current_technique_report_info(technique_name) before calling technique_name It needs the modification that is in ncf in #4806 that create the bundle that stores the technique name, both #4797 and update the logger_rudder to use this information #5330