ovsfw: no vm connectivity after nova reboot

[Inessa Vasilevskaya]

Seen on: multinode devstack (1 controller/1 compute)

Steps to reproduce:

1. boot a vm, verify that it can be reached
2. reboot the vm with nova reboot
3. check that the vm can't be reached anymore (on different deployments reproducibility varied from 50% to 100%)

The reason for connectivity loss is that ofport number corresponding to vm's tap interface doesn't match in_port number in ovs flows generated by the firewall. I suspect a race of some kind between tap interface plugging into br-int and the generation of ovs flows for a new vm.

Port numbers will match again after issuing nova shelve/unshelve.

no connectivity after reboot - http://paste.openstack.org/show/602726/
connectivity regained after shelve/unshelve - http://paste.openstack.org/show/602729/

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/newton
Review: https://review.openstack.org/447044

[IWAMOTO Toshihiro (iwamoto)]

Seems to be a duplicate of https://bugs.launchpad.net/neutron/+bug/1645655

[OpenStack Infra (hudson-openstack)]

Change abandoned by Inessa Vasilevskaya (<email address hidden>) on branch: stable/newton
Review: https://review.openstack.org/447044
Reason: duplicate, will be fixed by https://review.openstack.org/#/c/447772/