Description of problem:
on the latest puddle, I saw in logs those error after fresh install:
[root@controller-1 ~]# tail -f /var/log/openvswitch/ovsdb-server-nb.log
2017-10-01T10:09:06.369Z|04445|socket_util|ERR|6641:172.17.1.10: bind: Cannot assign requested address
2017-10-01T10:09:11.371Z|04450|socket_util|ERR|6641:172.17.1.10: bind: Cannot
2017-10-01T10:09:18.876Z|04456|ovsdb_jsonrpc_server|ERR|Dropped 56 log messages in last 58 seconds (most recently, 3 seconds ago) due to excessive rate
2017-10-01T10:09:18.876Z|04457|ovsdb_jsonrpc_server|ERR|ptcp:6641:172.17.1.10: listen failed: Cannot assign requested address
2017-10-01T10:09:21.370Z|04458|socket_util|ERR|6641:172.17.1.10: bind: Cannot assign requested address
the error exists on OVN slave nodes.
Version-Release number of selected component (if applicable):
(overcloud) [root@controller-0 ~]# rpm -qa |grep -i ovn
Steps to Reproduce:
1. Deploy Director HA 12 with OVN
2.check the log under /var/log/openvswitch/ovsdb-server-nb.log
The reason for these error logs is:
- In the case of OVN HA, ovsdb-server's are started in each controller as standby and then pacemaker promotes one as master on the node where VIP (ip-XXXXX) resource is started (because of colocation constraints set).
On all the controller nodes, ovsdb-servers are started with the option "--remote=ptcp:6641:VIP. Since the VIP is not present in the stand by nodes, the ovsdb-servers log the error messages.
Presently this is as expected. But the error logs could be annoying and I think it can be taken care in ovsdb-server to not log these error messages. Or may be don't open the socket if it's a standby server.
I would say its a low priority issue.
Submitted the patch in puppet-tripleo to set 'ip_nonlocal_bind' sysctl flag so that we don't see the error messages reported here.
fixed verified on :
12 -p 2017-11-14.4
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.