[ZBX-7378] wrong item/trigger IDs in DM node setup through master frontend Created: 2013 Nov 15  Updated: 2017 May 30  Resolved: 2015 May 20

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Frontend (F)
Affects Version/s: 2.2.0
Fix Version/s: None

Type: Incident report Priority: Critical
Reporter: Gerrit Fluck Assignee: Unassigned
Resolution: Won't fix Votes: 2
Labels: dm, items, triggers
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Debian Wheezy amd64, nginx + php-fpm

Attachments: JPEG File trigger_all.JPG     JPEG File trigger_node_selected.jpg    

 Description   

We have a node setup with 3 nodes (1 master and 2 child nodes), all gentoo 64 bit machines with same kernel

Master Node ID 1
--> Child Node ID3
--> Child Node ID4

If an item or trigger is created on a host on node ID 4 while "All" is checked as current node,
the item or trigger will get an item or trigger ID like 100100000015278 instead of 400100000015278
and is not synced to child database.

Frontend reports "Item created successfully", but the item/trigger is only visible while "All" Nodes is checked.
It is not shown when Node 4 is selected.

 Comments   
Comment by richlv [ 2015 May 20 ]

with nodes removed in 2.4, this one is unlikely to be looked in

Generated at Thu Apr 18 17:01:47 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.