Created attachment 1139090 [details]
ifcfg-ovs_bond0

Description of problem:

After adding a lacp ovs bond to br-ex as physical interface, creation of networks sometimes works fine and sometimes ends up with the ports beeing in 'binding_failed' state.

We have a Jenkins job that rebuilds the environment using PXE for OS installation, Packstack for OpenStack installation and some Ansible code for post-packstack configuration, including creation of provider network, router and private network. This works fine one day and ends up with neutron ports being in binding_failed state the other day, on the same commit of the automation code.

We started to see this error since we tried to use a lacp ovs bond as port to the physical network on br-ex. The lacp ovs bond as such can be used for ssh to the node.
Neutron openvswitch agent just reports:

Error received from [ovsdb-client monitor Interface name,ofport,external_ids --format=json]: None
Process [ovsdb-client monitor Interface name,ofport,external_ids --format=json] dies due to the error: None

Attached are the interface configuration files and logs. I will gladly provide any further info/config/logs that may help.


Version-Release number of selected component (if applicable):

yum list installed|egrep 'openvswitch|neutron'
openstack-neutron.noarch             1:7.0.1-1.el7            @openstack-liberty
openstack-neutron-common.noarch      1:7.0.1-1.el7            @openstack-liberty
openstack-neutron-ml2.noarch         1:7.0.1-1.el7            @openstack-liberty
openstack-neutron-openvswitch.noarch 1:7.0.1-1.el7            @openstack-liberty
openvswitch.x86_64                   2.4.0-1.el7              @openstack-liberty
python-neutron.noarch                1:7.0.1-1.el7            @openstack-liberty
python-neutronclient.noarch          3.1.0-1.el7              @openstack-liberty
python-openvswitch.noarch            2.4.0-1.el7              @openstack-liberty