[Openstack-security] [Bug 1290486] Re: neutron-openvswitch-agent does not recreate flows after ovsdb-server restarts

James Polley 1290486 at bugs.launchpad.net
Fri Jul 11 07:10:06 UTC 2014


I've tried to follow Roman's steps above, but I can't reproduce this
problem. I'm not sure if this is because I didn't quite do exactly the
same thing though.

I ran a standard devtest build from trunk, but with --no-undercloud, so
I've only got a seed and the overcloud.

9:04:17 0 130 polleyj at bill:~/.cache/tripleo (master)$ nova list
+--------------------------------------+-------------------------------------+--------+------------+-------------+--------------------+
| ID                                   | Name                                | Status | Task State | Power State | Networks           |
+--------------------------------------+-------------------------------------+--------+------------+-------------+--------------------+
| 2ccc4069-7801-4de2-8d22-a4da62aacb42 | overcloud-NovaCompute0-pok6xaae4p2j | ACTIVE | -          | Running     | ctlplane=192.0.2.3 |
| 4d99893a-be5f-48f9-8932-1123cdcaf3e0 | overcloud-NovaCompute1-fci7it3qq57q | ACTIVE | -          | Running     | ctlplane=192.0.2.6 |
| ba8dd7db-6189-4426-909d-84e63ec44c7b | overcloud-controller0-vyxuppnmkdf2  | ACTIVE | -          | Running     | ctlplane=192.0.2.4 |
+--------------------------------------+-------------------------------------+--------+------------+-------------+--------------------+

I sshed to 192.0.2.4 and used:

sudo ip netns exec qdhcp-8b8a6df3-f19f-4fa5-bed5-b13e5cbbe70c  ping
192.0.2.3

to try to ping out the right interface.

To restart the OVS, I sshed into 192.0.2.3 and ran "service openvswitch-
switch restart"

The ping running on the controller node didn't see any packets get
dropped.

Roman, am I missing some step from your process?

-- 
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):
  Incomplete
Status in neutron icehouse series:
  Fix Released
Status in tripleo - openstack on openstack:
  Fix Released

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




More information about the Openstack-security mailing list