dependancy problem 1.1.7

[kberrien]

Can anyone reproduce this on v1.1.7?

I create a trigger, and set a dependency from the drop down list to a host. IE, if this host is down (ping simple check), don't execute the trigger. I add the dependency. Page hangs, and after a few minutes eventually finishes. If I go back into the the trigger, its not shown.

If I show all my triggers, I see they all depend on my host.


So which setting is accurate? Is the dependency enabled or not? Or are you not supposed to make a host a dependency (then why is it available in the drop down list). Also, if a host is not a valid dependency, how does one say, ignore these routers down stream being offline if the first one is down....

[kberrien]

Additional

Just checked my test box running 1.1.6 (the 1.1.7 is our new production install), and I have a similar rule working without issue, pointing to a host. That box is Centos 4.4, with PHP 4, etc..

This new box, running 1.1.7 is Centos 5, php 5.1.6, httpd 2.2.3, mysql 5.0.22

[kberrien]

More info...

Well, as I've been creating other items on the production server, I was able to recreate other trigger with dependencies without issue.

After playing around, it appears you can't have a dependency with the same template as the trigger itself.

So if the trigger uses template ping_server_t

Your dependency can't use that same template. You can create a ping_server2_t and it will work fine. This should be fixed, otherwise you'll have to have tons of duplicate templates. To have a nested set of dependencies, one would be required to have tons of similar templates just to handle dependencies.

Also, if I have tens of devices using a template, but they have different dependencies, I have to use a different template for each different dependency. As triggers (which have dependencies) are related to templates its the only way. Dependencies should be related to hosts, or any have relations to both...