Skip to content

Icinga2 config not properly cleaned up after host is renamed or deleted

Originally created by @groente on #16125 (Redmine)

after renaming buse, the old buse.riseup.net entry in /etc/icinga2/zones.d was never cleaned up, which caused errors and prevented icinga2 from starting.
is this expected behaviour from the puppet module and did we simply forget to take a step in the renaming process and/or should something be fixed in the puppet code to prevent such an incident from occurring again?

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information