Hi all,
I've been using Zabbix 1.6 for quite a while. I successfuly upgraded from 1.6 to 1.6.1 to 1.6.2, etc. I stopped at 1.6.6. Everything was working fine (I did few patches in the frontend), but last week I decided to move to 1.8.1. The upgrade went fine and I had the system up & running in almost no time. Everything was properly imported from the previous version.
Unfortunately it looks like there is a big change in the way the dependencies work for triggers in 1.8. I have a generic templete called "Template_Windows_Workstations_Remote". It has items and triggers associated to some of the items. The interesting part is that I defined a "master trigger" called "Host is down" and all other triggers depends on this "master". The idea was no not trigger anything else as long as the machine is down.
There is a second template ("Template_Windows_Servers_Remote") which extends the base template with some additional items/triggers. It inherits all items/triggers from the base one. Everything was working fine in 1.6 and was even properly imported in 1.8. Now I want to add a new trigger in the base template and keep the dependency to the "master trigger". Unfortunately I cannot do this. I get an error saying that "Template_Windows_Workstations_Remote" is not the highest level template". I look over the code and it seems that now we check if there are any "derivated" templates and we don't allow dependencies in this case.
Like I said, this was working just fine in 1.6. I used this feature all the time. It is interesting that everything was properly imported (the dependency is there for triggers defined in 1.6) but I cannot add new ones. I even "simulated" the change of an existing trigger. I changed nothing by I tried to save it. Of course I couldn't do it. The errors pops up immediately. I don't understand how I cannot save it as long the dependence is already there and I don't change it.
Any ideas how to get arround it?
I've been using Zabbix 1.6 for quite a while. I successfuly upgraded from 1.6 to 1.6.1 to 1.6.2, etc. I stopped at 1.6.6. Everything was working fine (I did few patches in the frontend), but last week I decided to move to 1.8.1. The upgrade went fine and I had the system up & running in almost no time. Everything was properly imported from the previous version.
Unfortunately it looks like there is a big change in the way the dependencies work for triggers in 1.8. I have a generic templete called "Template_Windows_Workstations_Remote". It has items and triggers associated to some of the items. The interesting part is that I defined a "master trigger" called "Host is down" and all other triggers depends on this "master". The idea was no not trigger anything else as long as the machine is down.
There is a second template ("Template_Windows_Servers_Remote") which extends the base template with some additional items/triggers. It inherits all items/triggers from the base one. Everything was working fine in 1.6 and was even properly imported in 1.8. Now I want to add a new trigger in the base template and keep the dependency to the "master trigger". Unfortunately I cannot do this. I get an error saying that "Template_Windows_Workstations_Remote" is not the highest level template". I look over the code and it seems that now we check if there are any "derivated" templates and we don't allow dependencies in this case.
Like I said, this was working just fine in 1.6. I used this feature all the time. It is interesting that everything was properly imported (the dependency is there for triggers defined in 1.6) but I cannot add new ones. I even "simulated" the change of an existing trigger. I changed nothing by I tried to save it. Of course I couldn't do it. The errors pops up immediately. I don't understand how I cannot save it as long the dependence is already there and I don't change it.
Any ideas how to get arround it?
.
Comment