fullstack OVS agent in native openflow mode sometimes fails to bind socket
Bug #1576840 reported by
Assaf Muller
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
High
|
Unassigned |
Bug Description
Plenty of hits in the last few days, currently the top issue affecting fullstack stability.
Example paste:
http://
Changed in neutron: | |
assignee: | nobody → sudhakar kumar srivastava (sudhakar.srivastava) |
To post a comment you must log in.
Are we sending the individual fullstack log outputs to logstash/ elasticsearch? I don't get to make a decent query on logstash.. (I tried http:// logstash. openstack. org/#dashboard/ file/logstash. json?query= message% 3A%20%5C% 22error% 3A%20%5BErrno% 2098%5D% 20Address% 20already% 20in%20use% 5C%22 ).
I guess this is to concurrent runs of openvswitch agents trying to use the same port number?
If that's the case, could we retry tests runs on these cases, with random increments of port numbers? Or, it'd still be better if we could pass down to workers an incremental port-start-number to use when that is needed.