[ZBX-8313] Linked template dependency gets checked, before linking all templates Created: 2014 Jun 06 Updated: 2017 May 30 Resolved: 2014 Jun 16 |
|
| Status: | Closed |
| Project: | ZABBIX BUGS AND ISSUES |
| Component/s: | Server (S) |
| Affects Version/s: | 2.2.2 |
| Fix Version/s: | None |
| Type: | Incident report | Priority: | Major |
| Reporter: | Marco Hofmann | Assignee: | Unassigned |
| Resolution: | Won't fix | Votes: | 0 |
| Labels: | dependencies, templatelinking | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Zabbix Server 2.2.2 on Debian 7 |
||
| Description |
|
Detailed description in forum post: https://www.zabbix.com/forum/showthread.php?p=150817 --------------------------------------------------------------------- 11864:20140606:161631.142 cannot link template: trigger "RDP connect failed on {HOST.NAME}" in template "TEMPLATE_Customer OS Windows" has dependency from trigger "Ping Check Failed on {HOST.NAME}" in template "TEMPLATE_Customer ICMP Ping" The two templates "TEMPLATE_Customer OS Windows" & "TEMPLATE_Customer ICMP Ping" are linked. So in my eyes, this is a bug. You can't link linked templates which have dependencies, because they are checked, before both templates are linked. |
| Comments |
| Comment by Juris Miščenko (Inactive) [ 2014 Jun 16 ] |
|
This is not an error; this is the desired/expected behavior. Say you have Template B that has a trigger that depends on another trigger in Template A. The auto-registration actions state that Template B must be linked to the host upon creation, but it is not done, as there is no action that explicitly links Template A to the host. We do not link any dependency templates unless explicitly told to do so. Upon auto-registering a host, all dependencies of a linked template must be satisfied explicitly. |