To test this, check any provider network bridge after update, and make sure it's set as "standalone" For example, if you have br-ex # ovs-vsctl get-fail-mode br-ex standalone
Need the update OpenStack gerrit review number.
*** Bug 1397557 has been marked as a duplicate of this bug. ***
Note that this bug is affecting OSP 9 as well: ~~~ [root@overcloud-controller-0 ~]# ovs-vsctl get-fail-mode br-ex secure [root@overcloud-controller-0 ~]# ovs-ofctl dump-flows br-ex NXST_FLOW reply (xid=0x4): ~~~ ~~~ [root@overcloud-controller-0 ~]# rpm -qa | grep neutron openstack-neutron-bigswitch-lldp-2015.3.8-1.el7ost.noarch openstack-neutron-ml2-8.1.2-5.el7ost.noarch openstack-neutron-common-8.1.2-5.el7ost.noarch openstack-neutron-lbaas-8.0.0-1.el7ost.noarch python-neutron-lbaas-8.0.0-1.el7ost.noarch openstack-neutron-openvswitch-8.1.2-5.el7ost.noarch openstack-neutron-metering-agent-8.1.2-5.el7ost.noarch python-neutronclient-4.1.1-2.el7ost.noarch python-neutron-lib-0.0.2-1.el7ost.noarch openstack-neutron-bigswitch-agent-2015.3.8-1.el7ost.noarch python-neutron-8.1.2-5.el7ost.noarch openstack-neutron-8.1.2-5.el7ost.noarch ~~~ ~~~ [root@overcloud-controller-0 ~]# rpm -q --changelog openstack-neutron-8.1.2-5.el7ost.noarch | head * Wed Sep 14 2016 Hynek Mlnarik <hmlnarik> 1:8.1.2-5 - Set secure fail mode for physical bridges, rhbz#1372369 - Pass timeout in milliseconds to timer_wait, rhbz#1366187 ~~~ Do we already have a fix or BZ for OSP 9?
Yes, please see https://bugzilla.redhat.com/show_bug.cgi?id=1394890, found via this bug's dependency chain.
Verified on latest version openstack-neutron-7.2.0-5.el7ost.noarch According to following steps: 1) check <provider-net-bridge> ( br-ex) in standalone mode : 2) set the bridge to secure manually: sudo ovs-vsctl set-fail-mode <provider-net-bridge> secure 3) sudo service neutron-openvswitch-agent restart 4) check that it's gone back to standalone:
Will this be fixed in OSP 8??
Hello, Yes, this bug tracker is for OSP 8 and it will be fixed in versions >= openstack-neutron-7.2.0-3.el7ost (see the fields in the header section of this bugtracker)
Yes, this is targeted for our next update of osp 8.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2016-2988.html