Comment 4 for bug 1514056

Actually, it does.

In our production environment, hundreds of VM lost their network connection
because agents
 deleted all the flows even if the neutron servers were very busy.
We are still maintaining Neutron icehouse. The logical is the same with
HEAD.

We don't use tunnel yet. Only VLAN:
$ neutron net-show e8aba58a-6750-4e65-bf03-ab7c8875c310
....
| provider:network_type | vlan |
| provider:physical_network | physnet556 |
| provider:segmentation_id | 556 |

On Thu, Nov 26, 2015 at 10:01 PM, Ann Kamyshnikova <
<email address hidden>> wrote:

> @wenjianhn
>
> Yes, but dropping all flows on physical bridges does not led to vm's
> connectivity lost, so why is this need?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1514056
>
> Title:
> Set agent timestamp aka cookie to physical bridges
>
> Status in neutron:
> In Progress
>
> Bug description:
> Currently ovs agent only explicitly sets agent timestamp to br-int and
> br-tun bridges.
> Other physical bridges that are configured receive cookie=0x0 for their
> flows because the agent doesn't set timestamp for these bridges.
> Currently that doesn't lead to any malfunction, however it's better to
> provide a consistentsy over operations with bridges's flows.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/neutron/+bug/1514056/+subscriptions
>

--
Best,

Jian