Project

General

Profile

Bug #8840

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

Added by Kevin Kok over 3 years ago. Updated over 3 years ago.

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

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

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

Updated by Alexis MOUSSET over 3 years ago

  • Category set to Web - Config management
  • Target version set to 3.1.13
#2

Updated by François ARMAND over 3 years ago

Hi Kevin,

Thanks for the detailed report, it is much appreciated.

Node properties should start a promise generation, because as of http://www.rudder-project.org/redmine/issues/6733, they may be used in directive. As you discovred, it is the policy generation process that is responsible for creating/updating values in inputs/properties.d.

The problem will be corrected in next minors. As of their release, you can force a regeneration by going to Administration -> settings and "clear cache".

#3

Updated by François ARMAND over 3 years ago

  • Status changed from New to In progress
  • Assignee set to François ARMAND
#4

Updated by François ARMAND over 3 years ago

  • Related to User story #8848: Node properties update should create a change request added
#5

Updated by François ARMAND over 3 years ago

Here, I will simply correct the generation problem from API (as it's the only way to change properties today) but the general solution must be done in the related issue #8848

#6

Updated by François ARMAND over 3 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from François ARMAND to Vincent MEMBRÉ
  • Pull Request set to https://github.com/Normation/rudder/pull/1162
#7

Updated by François ARMAND over 3 years ago

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

Updated by Vincent MEMBRÉ over 3 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 3.1.13 and 3.2.6 which were released today.

Also available in: Atom PDF