Rudder

You have an interval defined to check your package right ?

And your first got a result susccess before having a noAnswer ?

This technique should keep the same result all over the interval.

Matthieu can you look into this ?

This bug may be related to #3964

For the record, this technique version 4.1 was introduced by #3793 on 2.6+ branches (and #3934 for 2.4 branch).

The only intent of this change was to reorder and hide some sections in the UI presentation. This shouldn't break reporting.

After checking, it seems that one of the variables changed in metadata.xml was moved into a multi-valued section, which it should not be in (RPM_PACKAGE_CHECK_INTERVAL), which means the .st file doesn't read this variable correctly. This is almost certainly the cause of this bug.

Ah, actually, there is a more severe problem, as this diff between 4.0 and 4.1 shows:

-      "package_number" int => readstringarrayidx("rpm_data","${sys.workdir}/inputs/rpmPackageInstallation/4.0/rpmPackageInstallationData", "#[^\n]*",":",9000,1600000);
+      "package_number" int => readstringarrayidx("rpm_data","${sys.workdir}/inputs/rpmPackageInstallation/3.0/rpmPackageInstallationData", "#[^\n]*",":",9000,1600000);

The Technique is trying to read pacakge names from a file in a different version number. This is probably the result of a bad merge, but needs fixing ASAP.

This PR is ready on the 2.4 branch: https://github.com/Normation/rudder-techniques/pull/198

BUT, it must be merged after the one from #3982 (https://github.com/Normation/rudder-techniques/pull/199).

Applied in changeset policy-templates:commit:140d7b4b25eff34bf840102edc09275f5ab8692d.