yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #18155
[Bug 1253993] Re: OVS agent loop slowdown
** Changed in: neutron
Status: In Progress => Fix Released
** Changed in: neutron
Milestone: None => juno-3
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1253993
Title:
OVS agent loop slowdown
Status in OpenStack Neutron (virtual network service):
Fix Released
Bug description:
This is probably a regression of bug #1194438
From several checks with parallel jobs, it seems agent loop becomes slower across iterations.
Slowness is not due to plugin RPC calls, which might be optimized anyway, but is mainly due to applying iptables/ovs configurations.
This consistently occurs in tempest tests with parallelism enabled.
Example logs here: http://logs.openstack.org/20/57420/5/experimental
/check-tempest-devstack-vm-neutron-isolated-parallel/54c6db3/logs
1 - OVS AGENT - Iteration #33 starts at 1:36:03
2 - Nova API - Server POST request at 1.39.42
3 - Neutron Server - Neutron POST /ports at 1.39.44
4 - OVS Agent OVS DB monitor detects instance's tap a 1.39.45
5 - OVS Agent - Iteration #33 completes processing device filters (security groups) at 1.39.51
6 - Nova API - Server ACTIVE by at 1.39.55
7 - Neutron Server - Floating IP POST at 1.39.55
8 - Neutron L3/VPN Agent - Floating IP ready at 1.40.37 (42 seconds???? - this should be another investigation)
9 - OVS Agent - Iteration #33 on OVS agent complete processing devices at 1.40.16
NOTE: The added device was not processed because the iteration started before the device was detected
10 - TEMPEST - TIMEOUT ON TEST at 1.40.56 - connection failed because internal port not wired
11 - OVS Agent - Iteration #33 completes processing ancillary ports at 1:42:07
12 - OVS Agent - Iteration #34 starts at 1:42:08
13 - OVS Agent - Iteration #34 completes processing device filters at 1:43:35
14 - The wiring of the interface for the server is not captured by the logs as the tempest test completed in the meanwhile.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1253993/+subscriptions