[dev.icinga.com #9267] Behaviour of node whitelist/blacklist

[icinga-migration]

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

Created by formorer on 2015-05-13 08:49:07 +00:00

Assignee: (none)
Status: New
Target Version: (none)
Last Update: 2017-01-14 13:07:03 +00:00 (in Redmine)

Icinga Version: 2.3.4
Backport?: Not yet backported
Include in Changelog: 1

---

On one of my systems I have the following blacklist filter:

blacklist filter for Node: '*' Host: '*' Service: '*'.

Which correctly ignores everything.

I now added the following whitelistfilter:
whitelist filter for Node: '' Host: 'i2-slave2.icinga.int' Service: ''.

But that doesn't work:

warning/cli: Skipping node 'i2-slave2.icinga.int' on blacklist.

What works is:

whitelist filter for Node: 'i2-slave2.icinga.int' Host: '*' Service: '*'.

That behaviour is at least unpexected and should be either adapted or fixed.

The terminus "node" and "zone" are also mixed, the parameter is talking about zone, whereas the
output talks about "node". That also needs some clarification

---

Parent Task: #13257

[icinga-migration]

Updated by mfriedrich on 2015-06-18 09:17:29 +00:00

• Category set to CLI
• Status changed from New to Assigned
• Assigned to set to jflach

[icinga-migration]

Updated by mfriedrich on 2015-06-23 13:27:24 +00:00

• Target Version set to Backlog

[icinga-migration]

Updated by mfriedrich on 2016-11-23 14:50:31 +00:00

• Status changed from Assigned to New
• Assigned to deleted jflach
• Target Version deleted Backlog
• Parent Id set to 13255

[icinga-migration]

Updated by mfriedrich on 2016-11-23 14:52:54 +00:00

• Parent Id deleted 13255

[icinga-migration]

Updated by mfriedrich on 2016-11-23 14:53:04 +00:00

• Relates set to 13255

[icinga-migration]

Updated by mfriedrich on 2017-01-14 13:06:42 +00:00

• Relates deleted 13255

[icinga-migration]

Updated by mfriedrich on 2017-01-14 13:07:03 +00:00

• Parent Id set to 13257

[dnsmichi]

#4799