Project

General

Profile

Actions

Bug #7452

closed

New version of ncf_conf.cache may not be properly updated on nodes after an upgrade

Added by Nicolas CHARLES about 9 years ago. Updated about 9 years ago.

Status:
Released
Priority:
1 (highest)
Assignee:
Jonathan CLARKE
Category:
System techniques
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

I upgraded on 3.2, and got 1 node out of 3 that did not upgrade its ncf.conf.cache file, resulting in the following errors

2015-11-24T09:55:02+0000    error: /default/rudder_directives/methods/'Configure network parameters/Configure network parameters'/default/Network_configuration/methods/'method_call'/default/file_ensure_keys_values/methods/'report'/default/_log/methods/'wrapper for _logger_default'/default/_logger_default: While constructing scope '_logger_default'
Formal =  {'message','old_class_prefix'}, Actual =  {'Ensure lines in format key=values into /etc/sysconfig/network','file_ensure_keys_values__etc_sysconfig_network','${class_prefix}','@{args}'}
2015-11-24T09:55:02+0000    error: /default/rudder_directives/methods/'Configure network parameters/Configure network parameters'/default/Network_configuration/methods/'method_call'/default/file_ensure_keys_values/methods/'report'/default/_log/methods/'wrapper for _logger_default'/default/_logger_default: Fatal CFEngine error: Augment scope, formal and actual parameter mismatch is fatal

The /var/rudder/ncf/local/ncf.conf is correct, so I don't know why it fails

Interestingly, the 2 nodes that succeedeed at updating it are both policy_server, and don't any meta techniques applied to them


Related issues 2 (0 open2 closed)

Related to Rudder - Bug #5937: Enforce the content of the local ncf configuration file from techniquesReleasedJonathan CLARKE2014-12-08Actions
Related to Rudder - Bug #8338: Invalid path for rudder_ncf in WindowsReleasedAlexis Mousset2016-05-19Actions
Actions

Also available in: Atom PDF