[17:53:47] <sukhe>	 hi folks, I could use some help if someone is around
[17:54:01] <sukhe>	 we have an Icinga check for "ns2-v4" that is currently CRITICAL and failing
[17:54:13] <sukhe>	 that is fine and expected, however I can't seem to understand where that check is coming from
[17:54:25] <sukhe>	 because it should have been removed and the puppet run on the alerting host confirms that
[17:55:20] <sukhe>	 https://puppetboard.wikimedia.org/report/alert1001.wikimedia.org/23038daaff39cc9f21c7304562af8181bbedc7a3
[17:55:26] <sukhe>	 any idea where else can this check live?
[17:59:35] <denisse>	 I'm unable to find references to that alert in our code. References to "ns2-v4" in our code are commented for the knams migration.
[18:00:35] <sukhe>	 is it fine if I try to reload icinga?
[18:00:47] <sukhe>	 I see ExecReload in the service
[18:01:00] <sukhe>	 should be a space operation in that sense, safer than restart 
[18:01:19] <denisse>	 I think that should be fine, I'm around in case the reload breaks something. :)
[18:01:33] <denisse>	 Could it be that the alert is cached by Icinga?
[18:01:50] <sukhe>	 denisse: I guess that's it but I don't know how and I have never seen it before :)
[18:01:54] <sukhe>	 thank you for the help
[18:01:56] <sukhe>	 I will try the reload
[18:02:35] <sukhe>	 ha
[18:02:38] <sukhe>	 that worked
[18:02:42] <sukhe>	 :)
[18:02:44] <sukhe>	 denisse: ^
[18:02:51] <denisse>	 Awesome!! :D
[18:02:55] <sukhe>	 I am quite confused
[18:03:02] <sukhe>	 but it's been a long week so if it works, I will take it :)
[18:03:27] <denisse>	 Thanks Sukhbir. My guess is that it was stuck in Icinga's cache.
[18:03:34] <sukhe>	 thanks for the help
[18:03:42] <denisse>	 Possibly an Icinga reload may be added to the cookbook used for decommissioning that host.
[18:04:34] <sukhe>	 in this case, there wasn't any decommissioning
[18:05:56] <sukhe>	 denisse: possibly that any removal requires a reload? I for some reason assumed it was automatic
[18:05:59] <sukhe>	 but TIL I guess