Reviewed: https://review.openstack.org/636719 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=84f8ae9d1f696b2561b634336338df0e14c37116 Submitter: Zuul Branch: master
commit 84f8ae9d1f696b2561b634336338df0e14c37116 Author: Rodolfo Alonso Hernandez <[email protected]> Date: Wed Feb 13 19:01:06 2019 +0000 Add "rpc_response_max_timeout" config variable in OVS agent The configuration variable "rpc_response_max_timeout" is not defined in the OVS agent configuration. When the agent is stopped (SIGTERM), the exception is raised. This error can be seen in the fullstack tests. Change-Id: Ieedb6e87a4e98efef0f895566f7d4d88c3cd9336 Closes-Bug: #1815797 ** Changed in: neutron Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1815797 Title: "rpc_response_max_timeout" configuration variable not present in OVS agent Status in neutron: Fix Released Bug description: The configuration variable "rpc_response_max_timeout" is not defined in the OVS agent. When the agent is stopped (SIGTERM), the exception is raised. This error can be seen in the fullstack tests. Error log: http://logs.openstack.org/52/636652/1/check/neutron- fullstack/91b459a/logs/dsvm-fullstack- logs/TestUninterruptedConnectivityOnL2AgentRestart.test_l2_agent_restart_OVS,VLANs ,openflow-cli_/neutron-openvswitch-agent--2019-02-13-- 15-54-07-617752.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1815797/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
