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

Trigger upgrade issue

    XMLWordPrintable

Details

    • Problem report
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 6.0.12
    • 6.0.13rc1, 6.2.7rc1, 6.4 (plan)
    • Server (S)
    • None
    • Upgrade to
      Zabbix server 4.0 -> 6.0
      Zabbix server 5.0 -> 6.0
    • Team A
    • Sprint 95 (Dec 2022), Sprint 96 (Jan 2023)
    • 0.5

    Description

      When upgrading from Zabbix 4.0 to 6.0, regular expressions in trigger evaluation are wrong.

      4.0
      {TEST Template:log["/test/test.log"].iregexp("C:\\Windows\\SystemApps\\Microsoft\.Windows\.test")}=0
      

      6.0
      find(/TEST Template/log["/test/test.log"],,"iregexp","C:\\Windows\\SystemApps\\MicrosoftWindowstest")=0
      

      Updating from 4.0 to 5.0 is no problem.
      Also, when xml exported in 4.0 is imported into 6.0, this phenomenon does not occur and is correct.

      Attachments

        1. 2zbx_export_hosts_with_LLD.yaml
          3 kB
        2. screenshot-1.png
          screenshot-1.png
          34 kB
        3. screenshot-2.png
          screenshot-2.png
          33 kB
        4. screenshot-3.png
          screenshot-3.png
          14 kB
        5. screenshot-4.png
          screenshot-4.png
          34 kB
        6. screenshot-5.png
          screenshot-5.png
          53 kB
        7. zabbix40_db.sql.gz
          1.22 MB
        8. Zabbix40_trigger.png
          Zabbix40_trigger.png
          40 kB
        9. Zabbix60_upgrade_trigger.png
          Zabbix60_upgrade_trigger.png
          42 kB
        10. zbx_export_hosts_subissue.yaml
          1.0 kB

        Issue Links

          Activity

            People

              wiper Andris Zeila
              hayato.watanabe Hayato Watanabe
              Votes:
              0 Vote for this issue
              Watchers:
              12 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: