Uploaded image for project: 'ZABBIX BUGS AND ISSUES'
  1. ZABBIX BUGS AND ISSUES
  2. ZBX-16574

[Manual close problem] Synchronizing the template's settings and hosts's settings

XMLWordPrintable

    • Icon: Problem report Problem report
    • Resolution: Won't fix
    • Icon: Critical Critical
    • None
    • 4.2.5
    • Server (S)
    • RedHat 7

      Steps to reproduce:

      1. Create discovery rules to discover mounted filesystems (for example) in the template
      2. Create trigger prototypes from that discovery inside the template
      3. Assing hosts to that template 
      4. After some time change settings of the triggers generated in the second step to be auto closable problem
      5. Try to auto close some problem which was generated by that triggeer before the step 4, but I can't, that trigger probably didn't collect "allow manual close" from the template 

      Result:
      See screenshot
      Expected:
      I expect that I can manually close all problems from some trigger. For example if I had a lot of false positive problems and if I decide to change setting to "allow manually close" I wouldn't be able to close them, only the new one created after the changes in trigger. 

        1. zabbix-bug1.png
          zabbix-bug1.png
          34 kB

          [ZBX-16574] [Manual close problem] Synchronizing the template's settings and hosts's settings

          Aleksandrs Petrovs-Gavrilovs added a comment -

          Hello,

          The triggers will be updates as soon as the LLD rules reruns, as the triggers are created from it. This is expected as per https://www.zabbix.com/documentation/4.2/manual/discovery/low_level_discovery

          This is expected behavior. So for now I will be closing the ticket as won't fix.

          Best Regards,
          Aleksandrs

          Aleksandrs Petrovs-Gavrilovs added a comment - Hello, The triggers will be updates as soon as the LLD rules reruns, as the triggers are created from it. This is expected as per  https://www.zabbix.com/documentation/4.2/manual/discovery/low_level_discovery This is expected behavior. So for now I will be closing the ticket as won't fix. Best Regards, Aleksandrs

            agavrilovs Aleksandrs Petrovs-Gavrilovs
            dsindicic Dario Sindicic
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: