I'm following pillar.example and having issues enabling extensive logging. If I remove extensive logging all is ok with rendering.
I noticed line 117 of named.conf.local.jinja seems to expect use_extensive_logging: would be a boolean.
ID: bind_local_config
Function: file.managed
Name: /etc/named.conf.local
Result: False
Comment: Unable to manage file: Jinja variable 'salt.utils.odict.OrderedDict object' has no attribute 'logging_config'
Started: 20:23:38.504949
Duration: 139.781 ms
Changes:
ID: bind
Function: service.running
Name: named
Result: False
Comment: One or more requisite failed: bind.config.bind_local_config
Started: 20:23:38.645581
Duration: 0.024 ms
Changes:
I'm following pillar.example and having issues enabling extensive logging. If I remove extensive logging all is ok with rendering.
I noticed line 117 of named.conf.local.jinja seems to expect use_extensive_logging: would be a boolean.
Pillar File ...
config: tmpl: salt://bind/files/redhat/named.conf user: root group: named mode: 640 enable_logging: true use_extensive_logging: channel: default_log: file: default size: '200m' versions: '10' print-time: yes print-category: yes print-severity: yes severity: info queries_log: file: queries print-time: yes print-category: yes print-severity: yes severity: info query-errors_log: file: query-errors print-time: yes print-category: yes print-severity: yes severity: dynamic default_syslog: print-time: yes print-category: yes print-severity: yes syslog: daemon severity: info default_debug: file: named.run print-time: yes print-category: yes print-severity: yes severity: info category: default:
...
Changed to following:
...
config: tmpl: salt://bind/files/redhat/named.conf user: root group: named mode: 640 enable_logging: true
...