[Bug 2127931] Re: 'ovsdb-client wait' does not accept multiple servers

Fri Mar 13 17:08:09 UTC 2026

The connecting/connected messages, in the case of needs-conversion work only for multiple servers. This is because, in open_rpc function, jsonrpc_session_run is only called in the case of multiple remotes (servers).
In the case of a single server no connecting/connected message is being printed. This might be ok for the case of needs-conversion which has more output, but in the case of wait it's the only message.

As we can see no connecting/connected message is printed when needs-
conversion is called with a single server.

root at microovn-1:~/ovs# ./ovsdb/ovsdb-client   -p
/var/snap/microovn/common/data/pki/client-privkey.pem   -c
/var/snap/microovn/common/data/pki/client-cert.pem   -C
/var/snap/microovn/common/data/pki/cacert.pem   -t 10 needs-conversion
ssl:10.75.96.207:6641 /snap/microovn/current/share/ovn/ovn-nb.ovsschema

2026-03-13T17:03:44Z|00001|ovsdb|WARN|/snap/microovn/current/share/ovn/ovn-nb.ovsschema: changed 2 columns in 'OVN_Northbound' database from ephemeral to persistent, including 'status' column in 'Connection' table, because clusters do not support ephemeral columns
no

If open_rpc is to be used then either a low level connection function
needs to be changed, or have a reply check in do_wait to check if reply
error is false and print similar status. (in that case info message will
show the ovsdb-client package instead of reconnect).

-- 
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to openvswitch in Ubuntu.
https://bugs.launchpad.net/bugs/2127931

Title:
  'ovsdb-client wait' does not accept multiple servers

Status in openvswitch package in Ubuntu:
  New

Bug description:
  Affected releases: The offending line [0] seems to be 7 years old, so
  I think pretty much all relevant releases

  The ovsdb-client should be able to `wait` on clustered database [1]:

  > ovsdb-client  supports  the  method1,method2,...,methodN syntax described in ovsdb(7) for connecting to a
    cluster.  When this syntax is used, ovsdb-client tries the cluster members in random order until it finds
    the cluster leader.  Specify the --no-leader-only option to instead accept any server that  is  connected
    to the cluster.

  However attempting to supply comma-separated list of connection
  methods results in failure.

  # First host works individually
  root at movn1:~# ovsdb-client -t 10 wait ssl:10.75.224.138:6641 OVN_Northbound connected
  2025-10-15T12:23:11Z|00001|reconnect|INFO|ssl:10.75.224.138:6641: connecting...
  2025-10-15T12:23:11Z|00002|reconnect|INFO|ssl:10.75.224.138:6641: connected

  # Second host works individually
  root at movn1:~# ovsdb-client -t 10 wait ssl:10.75.224.183:6641 OVN_Northbound connected
  2025-10-15T12:23:18Z|00001|reconnect|INFO|ssl:10.75.224.183:6641: connecting...
  2025-10-15T12:23:18Z|00002|reconnect|INFO|ssl:10.75.224.183:6641: connected

  The root cause seems to be parsing of the arguments in the `do_wait`
  function [0]. It can be compared to parsing for `do_needs_conversion`
  [2] where the multiple methods do work.

  [0] https://github.com/openvswitch/ovs/blame/ad0d646a3f6400c5c44655ae69d6e711270887ed/ovsdb/ovsdb-client.c#L2456
  [1] https://manpages.ubuntu.com/manpages/noble/man1/ovsdb-client.1.html
  [2] https://github.com/openvswitch/ovs/blame/ad0d646a3f6400c5c44655ae69d6e711270887ed/ovsdb/ovsdb-client.c#L1676

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/2127931/+subscriptions