Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[dev.icinga.com #12646] Sync rule for imports with filter only the last is used #434

Closed
icinga-migration opened this issue Sep 5, 2016 · 3 comments
Assignees

Comments

@icinga-migration
Copy link

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

Created by dgoetz on 2016-09-05 11:02:10 +00:00

Assignee: tgelf
Status: Feedback
Target Version: (none)
Last Update: 2016-10-14 06:54:56 +00:00 (in Redmine)


When i create a syncr rule to add imports based on a filter only the last one is evaluted (at least with 1.1 release).

An example: I have three templates "Linux", "Linux with Icinga 2 agent" and "Windows" which should be applied when the imported host has the matching filter "os=linux", "os=linux&agent=Icinga 2" and os="Windows". But it seems only the last is used as it was working fine with only linux hosts with agent and it broke when I added a windows host.

@icinga-migration
Copy link
Author

Updated by tgelf on 2016-10-13 16:39:43 +00:00

  • Status changed from New to Feedback
  • Assigned to set to dgoetz

Multiple properties with different filters should work fine, what do you mean by "it broke"?

@icinga-migration
Copy link
Author

Updated by dgoetz on 2016-10-14 06:54:56 +00:00

  • Assigned to changed from dgoetz to tgelf

It was not assigning the host template on the filter "os=linux&agent=Icinga 2" anymore after adding a third one with another filter so it seemed only the last one was evaluated. But perhaps this was fixed anyways, as Release 1.1 is quite old now.

Or do you means by multiple properties only multiple different not the the same multiple times with different filters?

@Thomas-Gelf
Copy link
Contributor

Talked to @dgoetz, problem should no longer exist.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants