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

unclear note in 3.4 compatibility page

    XMLWordPrintable

    Details

    • Type: Documentation task
    • Status: Closed
    • Priority: Trivial
    • Resolution: Fixed
    • Affects Version/s: 3.4.12
    • Fix Version/s: 4.0 (plan)
    • Component/s: None
    • Labels:
      None
    • Team:
      Team D
    • Sprint:
      Sprint 40, Sprint 41, Sprint 42

      Description

      https://www.zabbix.com/documentation/3.4/manual/appendix/compatibility says:

      3.4.10 version Zabbix servers are neither backward nor forward compatible with 3.4.x proxies.

      The note itself is rather cryptic, and nothing in particular stands out in the changelog when looking for PS entries:

      ........S. [ZBX-14333] fixed {ESC.HISTORY} and action log not to display colon without target host when executed on Zabbix server (vso)
      ........S. [ZBX-13043] removed error message for when user has defined media but all of them are disabled (viktors)
      ........S. [ZBX-14312] fixed possible deadlock in history syncer when housekeeper is deleting events (vso)
      ...G...PS. [ZBX-13782] fixed decoding of Unicode characters in JSON (Andris)
      .......PS. [ZBX-13788] fixed host availability stuck in unknown state after proxy changes (wiper)
      ........S. [ZBX-12372] fixed duplication of prefix "/" for second parameter "path" in items "web.page.*" (MVekslers)
      

      It would be great to clarify this note. Additionally, the note in https://www.zabbix.com/documentation/3.4/manual/installation/upgrade_notes_3410 would benefit from the same clarification.

        Attachments

          Activity

            People

            Assignee:
            martins-v Martins Valkovskis
            Reporter:
            richlv richlv
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: