mirror of
https://gitlab.freedesktop.org/NetworkManager/NetworkManager.git
synced 2025-12-28 11:00:09 +01:00
ovsdb: downgrade error logging to warnings
<error> is mostly about "really should not happen" scenarios. It's closer to an assertion failure, and something that NetworkManager should not happen. Of course, things can go wrong, but <warn> is a sufficient. When ovsdb gives unexpected communication, it's just a warning. At least, that's also what all the similar cases in "nm-ovsdb.c" already do
This commit is contained in:
parent
25c97817d2
commit
0ee60b943d
1 changed files with 2 additions and 2 deletions
|
|
@ -2274,13 +2274,13 @@ ovsdb_got_msg(NMOvsdb *self, json_t *msg)
|
|||
|
||||
/* This is a response to a method call. */
|
||||
if (c_list_is_empty(&priv->calls_lst_head)) {
|
||||
_LOGE("there are no queued calls expecting response %" G_GUINT64_FORMAT, (guint64) id);
|
||||
_LOGW("there are no queued calls expecting response %" G_GUINT64_FORMAT, (guint64) id);
|
||||
ovsdb_disconnect(self, FALSE, FALSE);
|
||||
return;
|
||||
}
|
||||
call = c_list_first_entry(&priv->calls_lst_head, OvsdbMethodCall, calls_lst);
|
||||
if (call->call_id != id) {
|
||||
_LOGE("expected a response to call %" G_GUINT64_FORMAT ", not %" G_GUINT64_FORMAT,
|
||||
_LOGW("expected a response to call %" G_GUINT64_FORMAT ", not %" G_GUINT64_FORMAT,
|
||||
call->call_id,
|
||||
(guint64) id);
|
||||
ovsdb_disconnect(self, FALSE, FALSE);
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue