Project

General

Profile

Actions

Bug #8840

closed

Node properties are not being synchronized on the node itself until promises are created/modified

Added by Kevin Kok about 8 years ago. Updated about 8 years ago.

Status:
Released
Priority:
N/A
Category:
Web - Config management
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

As specified in the documentation, node properties are synchronized on the node (in /var/rudder/cfengine-community/inputs/properties.d) when the promises are being generated/updated.

However if node properties are changed, and no other promises are being created or modified, the node properties won't get updated, even when trying to force updating the agent promises (rudder agent update -f && rudder agent run).

This is an issue when node properties are being used in current promises, as they will still map to the old values.


Related issues 1 (1 open0 closed)

Related to Rudder - User story #8848: Node properties update should create a change requestNewActions
Actions

Also available in: Atom PDF