Project

General

Profile

Actions

Bug #9402

closed

Node properties update doesn't invalidate node configuration hash

Added by François ARMAND over 4 years ago. Updated over 4 years ago.

Status:
Released
Priority:
1
Category:
Web - Config management
Target version:
Severity:
User visibility:
Effort required:
Priority:

Description

If node properties are updated, and the properties are not used in a directive, then the node configuration hash is not updated. This is problematic because it means that the file .../properties.d/properties.json is not correctly synch with the real node properties.

Actions #1

Updated by François ARMAND over 4 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from François ARMAND to Nicolas CHARLES
  • Pull Request set to https://github.com/Normation/rudder/pull/1284
Actions #2

Updated by François ARMAND over 4 years ago

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

Updated by Vincent MEMBRÉ over 4 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 4.0.1, 3.1.16 and 3.2.10 which were released today.

Actions

Also available in: Atom PDF