Project

General

Profile

Actions

Bug #3965

closed

Technique 'Package management for RHEL / CentOS / SuSE / RPM systems' v4.1: Reportings are in No Answer state

Added by Dennis Cabooter over 9 years ago. Updated over 9 years ago.

Status:
Released
Priority:
2
Category:
Techniques
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Regression:

Description

The title says it all. Unfortunatly I had to migrate back to technique version 4.0 to get all working again.


Related issues 1 (0 open1 closed)

Blocked by Rudder - Bug #3982: Technique 'Package management for RHEL / CentOS / SuSE / RPM systems' v4.1: patch_commands have been wrongly backported to 2.4 branchReleasedNicolas CHARLES2013-10-02Actions
Actions #1

Updated by Vincent MEMBRÉ over 9 years ago

  • Assignee set to Matthieu CERDA
  • Priority changed from N/A to 3

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

Actions #2

Updated by Jonathan CLARKE over 9 years ago

  • Status changed from New to In progress
  • Assignee changed from Matthieu CERDA to Jonathan CLARKE
  • Target version changed from 2.6.6 to 2.4.10

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.

Actions #3

Updated by Jonathan CLARKE over 9 years ago

  • Priority changed from 3 to 2

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.

Actions #4

Updated by Jonathan CLARKE over 9 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Jonathan CLARKE to Nicolas CHARLES
  • Pull Request set to https://github.com/Normation/rudder-techniques/pull/198

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).

Actions #5

Updated by Jonathan CLARKE over 9 years ago

  • Status changed from Pending technical review to Pending release
  • % Done changed from 0 to 100

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

Actions #6

Updated by Nicolas PERRON over 9 years ago

  • Target version changed from 2.4.10 to 2.4.9
Actions #7

Updated by Nicolas PERRON over 9 years ago

  • Subject changed from Packages on Red Hat get status No Answer with technique version 4.1 to Technique 'Package management for RHEL / CentOS / SuSE / RPM systems' v4.1: Reportings are in No Answer state
Actions #8

Updated by Nicolas PERRON over 9 years ago

This bug has been fixed in Rudder 2.4.9, which was released today.
Check out:

Actions #9

Updated by Nicolas PERRON over 9 years ago

  • Status changed from Pending release to Released
Actions

Also available in: Atom PDF