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

host.update API method requires tls_psk_identity when it shouldn't

    XMLWordPrintable

    Details

    • Type: Incident report
    • Status: Closed
    • Priority: Minor
    • Resolution: Duplicate
    • Affects Version/s: 3.2.1
    • Fix Version/s: None
    • Component/s: API (A)
    • Labels:
    • Environment:
      Zabbix server is running on Scientific Linux 7.2, using RPMs from repo.zabbix.com (3.2.1-1.el7_x86_64)
    • Team:
      Team C
    • Sprint:
      Sprint 4, Sprint 5, Sprint 6, Sprint 7
    • Story Points:
      0.5

      Description

      I'm attempting to update groups for a host via the API using the host.update method. I would expect that the only parameters I would have to give are what is being changed. However, the API errors, insisting that I also send it the tls_psk_identity (and tls_psk as well if I only add tls_psk_identity). Node is configured to use encryption and everything else is working correctly. I can work around the issue by submitting the same encryption info I did when I set up the node.

       {
        "code": -32602,
        "message": "Invalid params.",
        "data": "Incorrect value for field \"tls_psk_identity\": cannot be empty."
      }
      

      on request:

       {
        "method": "host.update",
        "params": [
          {
            "hostid": 10137,
            "groups": [
              "11"
            ]
          }
        ],
        "id": 70397,
        "jsonrpc": "2.0",
        "auth": "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
      }
      

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              russjury Russ Jury
              Votes:
              2 Vote for this issue
              Watchers:
              6 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: