Actions
Bug #9402
closedNode 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.
Actions