commit f6d98a747b03e4da5109b2ee0e3c1bd7e88aee49
Author: Bernard Cafarelli <email address hidden>
Date: Mon Aug 27 14:37:15 2018 +0200
ovsdb monitor: do not die on ovsdb-client stderr output
That process may generate stderr output (ovs 2.10 with dpdk support will
log about missing optional libraries for example), in which case the
agent will loop forever respawning the ovsdb-client processes.
AsyncProcess already handles processes exiting uncleanly, and logs
stderr output with log_output=True (which is the case for OvsdbMonitor).
As the monitors work on stdout output, disabling die_on_error is enough
to make them work with this behaviour.
Reviewed: https:/ /review. openstack. org/596717 /git.openstack. org/cgit/ openstack/ neutron/ commit/ ?id=f6d98a747b0 3e4da5109b2ee0e 3c1bd7e88aee49
Committed: https:/
Submitter: Zuul
Branch: master
commit f6d98a747b03e4d a5109b2ee0e3c1b d7e88aee49
Author: Bernard Cafarelli <email address hidden>
Date: Mon Aug 27 14:37:15 2018 +0200
ovsdb monitor: do not die on ovsdb-client stderr output
That process may generate stderr output (ovs 2.10 with dpdk support will
log about missing optional libraries for example), in which case the
agent will loop forever respawning the ovsdb-client processes.
AsyncProcess already handles processes exiting uncleanly, and logs
stderr output with log_output=True (which is the case for OvsdbMonitor).
As the monitors work on stdout output, disabling die_on_error is enough
to make them work with this behaviour.
Change-Id: I8f2e5b93b9c16f 9b288046911b5ae b4938845233
Closes-Bug: #1788865