Actions
Bug #9402
closed
Node properties update doesn't invalidate node configuration hash
Status:
Released
Priority:
1 (highest)
Assignee:
Category:
Web - Config management
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
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.
Updated by François ARMAND about 8 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
Updated by François ARMAND about 8 years ago
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset rudder|a7df590f3c2c06853e812184f8bf213995ddf721.
Updated by Vincent MEMBRÉ about 8 years ago
- Status changed from Pending release to Released
Actions