wrong item/trigger IDs in DM node setup through master frontend

XMLWordPrintable

    • Type: Incident report
    • Resolution: Won't fix
    • Priority: Critical
    • None
    • Affects Version/s: 2.2.0
    • Component/s: Frontend (F)
    • Environment:
      Debian Wheezy amd64, nginx + php-fpm

      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.

            Assignee:
            Unassigned
            Reporter:
            Gerrit Fluck
            Votes:
            2 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: