[L2][scale issue] ovs-agent has too many flows to do trouble shooting
Bug #1813708 reported by
LIU Yulong
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
When subnets or security group ports quantity reach 2000+, it is really too hard to do trouble shooting if one VM lost the connection. The flow tables are almost unreadable (reach 30k+ flows). We have no way to check the ovs-agent flow status. And restart the L2 agent does not help anymore, since we have so many issue at scale.
This is a subproblem of bug #1813703, for more information, please see the summary:
https:/
tags: | added: neutron-proactive-backport-potential |
Changed in neutron: | |
status: | New → Fix Released |
To post a comment you must log in.
Not sure what you meant by 'flow tables are almost unreadable'?
Is this really a bug or human capability to read from 30k+ flows after filtering.
Can we filter and read the flows or since it is busy we are not able to even dump the flows?