Rudder

Alexis MOUSSET wrote:

I see regularly, on some machines, these two message fro the same component:

• No action required for ...
• RPM package ... was correct

The first report comes from a hardcoded success report in the technique:

      "any" usebundle => rudder_common_report_index("packageInstallation", "result_success", "${rpm_data[${index_rpmpkg}][3]}", "RHEL/CentOS/SuSE packages", "${rpm_package[${index_rpmpkg}]}", "No action required for RPM package ${rpm_package[${index_rpmpkg}]} with policy: ${rpm_data[${index_rpmpkg}][0]}", "${index_rpmpkg}"),
        ifvarclass => "is_update_action_${index_rpmpkg}.!${index_rpmpkg}_package_version_defined.(rpm_package_installation_updated_available_packages_kept|rpm_package_installation_updated_available_packages_repaired).!${index_rpmpkg}_update_version_valid";

This second report comes from a call to:

rudder_common_reports_generic_index(..., "rpm_package_installation_${index_rpmpkg}", ..., "RPM package ${rpm_package[${index_rpmpkg}]} with policy: ${rpm_data[${index_rpmpkg}][0]}")

There is a high chance this bug was caused by #8421. That would be the case if you only saw this double reporting just after a policy update on the node, which may or may not coincide (but probably does) with a change in the directive's settings.

Could you check to see if you still get this with the fix for #8421 please Alexis?

Jonathan CLARKE wrote:

There is a high chance this bug was caused by #8421. That would be the case if you only saw this double reporting just after a policy update on the node, which may or may not coincide (but probably does) with a change in the directive's settings.

Could you check to see if you still get this with the fix for #8421 please Alexis?

Tests seem to have confirmed this was fixed by #8421. Closing as a duplicate.