yahoo-eng-team team mailing list archive

[IWAMOTO Toshihiro <iwamoto@xxxxxxxxxxxxx>]

*** This bug is a duplicate of bug 1645655 ***
    https://bugs.launchpad.net/bugs/1645655

** This bug has been marked a duplicate of bug 1645655
   ovs firewall cannot handle server reboot

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1673027

Title:
  ovsfw: no vm connectivity after nova reboot

Status in neutron:
  In Progress

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://paste.openstack.org/show/602726/
  connectivity regained after shelve/unshelve - http://paste.openstack.org/show/602729/

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1673027/+subscriptions