ovsfw: no vm connectivity after nova reboot
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
In Progress
|
Undecided
|
Inessa Vasilevskaya |
Bug Description
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://
connectivity regained after shelve/unshelve - http://
Changed in neutron: | |
assignee: | nobody → Inessa Vasilevskaya (ivasilevskaya) |
Changed in neutron: | |
status: | New → In Progress |
Fix proposed to branch: stable/newton /review. openstack. org/447044
Review: https:/