yahoo-eng-team team mailing list archive

[Ed Bak <ed.bak2@xxxxxx>]

Public bug reported:

The rpc call get_devices_details_list made from within the
neutron_openvswitch_agent can timeout as an environment scales up and
the port list grows.  This prevents the neutron_openvswitch_agent from
starting successfully.  Increasing the rpc_response_timeout is one
solution but doesn't seem to be ideal.  Another solution is to
repeatedly call get_devices_details_list with a fixed subset size of
devices.  The subset size could be set so that the rpc call always
completes within the default rpc_response_timeout and a timeout failure
would be independent of scale.

** Affects: neutron
     Importance: Undecided
     Assignee: Ed Bak (ed-bak2)
         Status: New

** Changed in: neutron
     Assignee: (unassigned) => Ed Bak (ed-bak2)

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1430999

Title:
  get_devices_details_list times out in a scaled up environment

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  The rpc call get_devices_details_list made from within the
  neutron_openvswitch_agent can timeout as an environment scales up and
  the port list grows.  This prevents the neutron_openvswitch_agent from
  starting successfully.  Increasing the rpc_response_timeout is one
  solution but doesn't seem to be ideal.  Another solution is to
  repeatedly call get_devices_details_list with a fixed subset size of
  devices.  The subset size could be set so that the rpc call always
  completes within the default rpc_response_timeout and a timeout
  failure would be independent of scale.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1430999/+subscriptions