Open Stack

Still seeing this with neutron as of commit 53b701a3f91530c9462a9cb0690aaf68efd45f6d
(ubuntu saucy, linux 3.11, openvswitch-server 1.10.2)

Steps to reproduce:
1. Run devtest.sh
2. Start pinging a user VM using the floating ip.
3. ssh to the controller node.
4. Do: sudo service openvswitch-switch restart

The user VM becomes unreachable until neutron-openvswitch-agent is
restarted on the controller node.

** Changed in: tripleo
       Status: Fix Committed => Triaged

-- 
You received this bug notification because you are a member of OpenStack
Security Group, which is subscribed to OpenStack.
https://bugs.launchpad.net/bugs/1290486

Title:
  neutron-openvswitch-agent does not recreate flows after ovsdb-server
  restarts

Status in OpenStack Neutron (virtual network service):
  Fix Committed
Status in neutron icehouse series:
  In Progress
Status in tripleo - openstack on openstack:
  Triaged

Bug description:
  The DHCP requests were not being responded to after they were seen on
  the undercloud network interface.  The neutron services were restarted
  in an attempt to ensure they had the newest configuration and knew
  they were supposed to respond to the requests.

  Rather than using the heat stack create (called in
  devtest_overcloud.sh) to test, it was simple to use the following to
  directly boot a baremetal node.

      nova boot --flavor $(nova flavor-list | grep "|[[:space:]]*baremetal[[:space:]]*|" | awk '{print $2}) \
            --image $(nova image-list | grep "|[[:space:]]*overcloud-control[[:space:]]*|" | awk '{print $2}') \
            bm-test1

  Whilst the baremetal node was attempting to pxe boot a restart of the
  neutron services was performed.  This allowed the baremetal node to
  boot.

  It has been observed that a neutron restart was needed for each
  subsequent reboot of the baremetal nodes to succeed.

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