Nodes from Foreman were accidently removed in Icinga2

Icinga Web Modules Icinga Director
1

Hi all,

we are using Icinga2 with the director and we fetch all the nodes directly from Foreman via REST API.

Some time ago the Foreman VM had an issue and was not available. As a result of which all hosts were removed from Icinga2, because the automation in the director was not able to fetch them but got a 503 instead. Then we fixed the Foreman VM and all hosts reappeared in Icinga2 aswell.

Is there any way to prevent the nodes from accidently removal due to an error of an external data source like Foreman? Same applies for services that are fetched from the PuppetDB or any other sources.

  • Director version (System - About): 1.8.0
  • Icinga Web 2 version and modules (System - About): 2.8.2
  • Icinga 2 version (icinga2 --version): r2.12.4-1
  • Operating System and version: Debian 10.10
  • Webserver, PHP versions: Apache2 2.4.38-3+deb10u5 / PHP 7.3.29-1~deb10u1

Best regards, Christian

2

I would consider this as a bug as the import should clearly differentiate between no data provided and import source not available, and 5xx returncodes should be the later. So can you open a bug against the director?