Rudder

I have no idea how, but I ended up with wrongly generated promises.cf, leading to rudder executing the generic method without reporting context and so, correct reporting.
here is the output of one part of the promises.cf on the server:

bundle common va
{
  vars:

      "end" slist => {
        "endExecution" 
      };

      "common_bs" slist => {
        "startup",
        "check_disable_agent",
        "update_reports",
        "configuration",
        "initialize_ncf",
        "internal_security",
        "check_cf_processes",
        "check_uuid",
        "garbage_collection",
        "setup_cronjob",
        "check_cron_daemon",
        "doInventory",
      };

    policy_server::

      "specific_bs" slist => {
        "install_rsyslogd",
        "propagatePromises",
        "sendInventoryToCmdb",
        "root_component_check",
        # This bundle is duplicated to avoid having empty lists and cfnull in bundlesequence
        "check_binaries_freshness",
      };

    !policy_server::

and on a fonctionnal one:

 bundle common va
 {
   vars:

       "end" slist => {
         "restart_services",
         "monitoring_hook_post",
         "endExecution" 
       };

       "common_bs" slist => {
         "startup",
         "check_disable_agent",
         "update_reports",
         "configuration",
         "initialize_ncf",
         "internal_security",
         "check_cf_processes",
         "check_uuid",
         "garbage_collection",
         "setup_cronjob",
         "check_cron_daemon",
         "configure_rudder_reporting_system",
         "check_zypper",
         "get_environment_variables",
         "properties",
         "nxlog_enable",
         "monitoring_hook_pre",
       };

     policy_server::

       "specific_bs" slist => {
         # This bundle is duplicated to avoid having empty lists and cfnull in bundlesequence
         "check_binaries_freshness",
       };

The reports are unparsable, and end up in the following syntax:

@@@@log_info@@@@Check apache boot script@@apache2@@2019-04-08 09:39:51+00:00##root@#Ensure service apache2 is started at boot was correct

Regenerating the policies, fixing the pb in it (I had a typo in a generic method I was developping) fixed the problem.