Actions
Bug #6673
closedNo reporting on agents on ncf directives on SLES
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
On SLES 11, when using directives from ncf, there is no reporting from agent nodes. It happens because the agent does not use the ncf logger (but only the default logger).
On the agent:
cat /var/rudder/cfengine-community/ncf.conf.cache # This file can be used to adjust some elements in ncf. # # With CFEngine 3.6 or more, this is a Mustache template file, and allows variation # of configuration based on CFEngine classes # see http://mustache.github.io/ for the full mustache specification # and https://docs.cfengine.com/docs/3.6/reference-promise-types-files.html for # CFEngine implementation # # If you are using CFEngine 3.5, only lines with key=value will be read # and no class specific configuration can apply # # Which logger(s) should be used in ncf? (comma separated list) loggers=_logger_default # Which port should be for CFEngine connections/data transfers cfengine_port=5308
It appears that the agent does not have the right "g.rudder_ncf_origin_local" value, and uses the default (/var/rudder/configuration-repository/ncf), which only exists on the server. The problem disappears when changing site.cf from:
# defines the path to the ncf configuration file bundle common ncf_configuration { vars: "ncf_configuration_file" string => "${g.rudder_ncf_origin_local}/ncf.conf"; }
To:
# defines the path to the ncf configuration file bundle common ncf_configuration { vars: "ncf_configuration_file" string => "/var/rudder/ncf/local/ncf.conf"; }
The problem does not occur on CentOS.
Actions