disabled triggers are suddenly back

[harri]

Hi folks,

If I relink a set of hosts to another template, then the "disabled" settings in the new template are ignored :-(.

To reproduce:

I've got 2 templates: A and A' (an unmodified clone of A). My hosts are linked to A.

If I relink some hosts to A' using mass update, and then disable some triggers in A', then the hosts linked to A' get their triggers disabled, respectively, as expected. If I relink the remaining hosts from A to A', then this second set of hosts has all triggers enabled, even those disabled in A'.

Looking at the triggers in the host configuration I see the A' triggers only for all hosts.
Zabbix is version 1.8.3.

This is extremely painful, since it makes the configuration using templates unreliable. How can I fix this?


Any helpful comment would be highly appreciated.

Harri

[untergeek]

If A and A' are identical, you are experiencing colliding triggers and item keys. To prevent collisions, you should never have items with identical keys in different templates, nor should templates have application names identical to those in other templates (more collisions).

[harri]

Of course they are not _that_ identical. A and A' use their own namespace for item and trigger names. I created A' following the sample procedure in the Zabbix book.