I'm moving state to incomplete and lowering priority so the bug is not weighting on mos-neutron team.
The repro cases that we've seen show that the reason was due to ovs agent was not able to receive information from neutron-server during rabbitmq outage that was caused by Fuel monitoring.
So right now https://bugs.launchpad.net/mos/+bug/1423404 is considered as a root cause of this issue.
There's not much that could be done on neutron (ovs agent) side.
I'm moving state to incomplete and lowering priority so the bug is not weighting on mos-neutron team.
The repro cases that we've seen show that the reason was due to ovs agent was not able to receive information from neutron-server during rabbitmq outage that was caused by Fuel monitoring. /bugs.launchpad .net/mos/ +bug/1423404 is considered as a root cause of this issue.
So right now https:/
There's not much that could be done on neutron (ovs agent) side.
We will reopen bug if this analysis is wrong.