[dev.icinga.com #12949] contents of templates.conf not managed, leading to re-defined objects

[icinga-migration]

This issue has been migrated from Redmine: https://dev.icinga.com/issues/12949

Created by pavo on 2016-10-20 15:59:22 +00:00

Assignee: (none)
Status: New
Target Version: (none)
Last Update: 2016-10-21 16:03:35 +00:00 (in Redmine)

---

Hi,

I'm pretty new to Icinga2 and the cookbook, so I might be missing something.

The issue I'm observing is that when using included server recipe example, duplicate definition is created causing icinga2 to fail to start. The error I'm getting is
critical/config: Error: Object 'mail-host-notification' of type 'Notification' re-defined: in /etc/icinga2/objects.d/notification_template.conf: 10:1-10:46; previous definition: in /etc/icinga2/conf.d/templates.conf: 46:1-46:46

While /etc/icinga2/objects.d/notification_template.conf is managed by chef, contents of /etc/icinga2/conf.d/templates.conf are left as is, as provided by the package during installation.

Steps to reproduce:

• have a clean Ubuntu box
• put these 2 recipes in the node's run_list: recipe[icinga2::server], recipe[icinga2_server] (the latter is taken from the included example)
• run chef-client

Thanks

[icinga-migration]

Updated by pavo on 2016-10-21 16:03:35 +00:00

After taking longer look, it seems to me that the idea of this cookbook may be to store all configs in objects.d, not using conf.d at all.
Having node['icinga2']['disable_conf_d'] set to false prevents Icinga to include configs from conf.d, and though will get rid of the issue.
Perhaps worth setting as default in cookbook attributes file? Or maybe including a role example? I've done that with role in my case.

[vkhatri]

Will update the documentation.

[vkhatri]

I think you meant to say setting node['icinga2']['disable_conf_d'] to true.
It is fair to set it true as default resources are also created by cookbook.

Please feel free to submit a PR.

[vkhatri]

Cookbook updated.