yahoo-eng-team team mailing list archive

[Thierry Carrez <thierry.carrez+lp@xxxxxxxxx>]

** Changed in: neutron
       Status: Fix Committed => 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/1254520

Title:
  Open vSwitch commands timeout on gate tests

Status in OpenStack Neutron (virtual network service):
  Fix Released

Bug description:
  Error 242 occurs fairly often in gate tests:
  http://logstash.openstack.org/#eyJzZWFyY2giOiJcIkV4aXQgY29kZTogMjQyXCIgIiwiZmllbGRzIjpbImZpbGVuYW1lIl0sIm9mZnNldCI6MCwidGltZWZyYW1lIjoiNDMyMDAiLCJncmFwaG1vZGUiOiJjb3VudCIsInRpbWUiOnsidXNlcl9pbnRlcnZhbCI6MH0sInN0YW1wIjoxMzg1MzE3OTg4NTQxLCJtb2RlIjoiIiwiYW5hbHl6ZV9maWVsZCI6IiJ9

  This is actual an ALARM_CLOCK error [142] (rootwrap adds 100 to the
  error code), and means open vswitch times out; as the default timeout
  is 2 seconds there is a chance they could occur quite often in a
  rather stressful scenario as the one represented by parallel tests in
  tenant isolation.

  It might be therefore advisable to allow for a configurable timeout on
  ovs commands, and increase this timeout for gate tests.

  Kernel logs do not provide enough additional information.
  It might be also worth adding open vswitch logs to the logs collected by devstack-gate

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