summaryrefslogtreecommitdiff
path: root/Documentation/ref
diff options
context:
space:
mode:
authorAlexey Roytman <roytman@il.ibm.com>2021-06-15 15:01:47 +0300
committerBen Pfaff <blp@ovn.org>2021-07-07 13:32:04 -0700
commitb30bfb6b8db19c8696592ed325e64ed208bc4438 (patch)
tree770888c9dd8226a0b4cbd596e1f30919f12a2a40 /Documentation/ref
parent0c0995238241a7e41b434dc4a1ff3660efa581e5 (diff)
downloadopenvswitch-b30bfb6b8db19c8696592ed325e64ed208bc4438.tar.gz
ovsdb-server.7.rst Fix response result of monitor_cond_change
The original version said that "monitor_cond_change" request response should contain '"result": null'. However, if response message has form like {"id":13, "result":null} or {"id":13} the ovsdb client (ovn-controller) returns the folling misleading message and closes connection. 2021-06-07T14:32:30.116Z|00026|jsonrpc|WARN|tcp:172.18.0.4:6642: received bad JSON-RPC message: request must have "method" 2021-06-07T14:32:30.116Z|00027|reconnect|WARN|tcp:172.18.0.4:6642: connection dropped (Protocol error) Signed-off-by: Alexey Roytman <roytman@il.ibm.com> Signed-off-by: Ben Pfaff <blp@ovn.org>
Diffstat (limited to 'Documentation/ref')
-rw-r--r--Documentation/ref/ovsdb-server.7.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/ref/ovsdb-server.7.rst b/Documentation/ref/ovsdb-server.7.rst
index 04414350a..e1dca6dca 100644
--- a/Documentation/ref/ovsdb-server.7.rst
+++ b/Documentation/ref/ovsdb-server.7.rst
@@ -304,7 +304,7 @@ monitoring session.
The response object has the following members::
- "result": null
+ "result": {}
"error": null
"id": same "id" as request