There is no connectivity to intsance over floating ip after l3 agent rescheduling and destroy/reset controller

[Tatyanka]

Steps:
Check l3-agent rescheduling after reset non-primary controller
for vxlan

Scenario:
1. Revert snapshot with neutron cluster
2. Create an instance with a key pair
3. Manually reschedule router from primary controller
to another one
4. Reset controller with l3-agent
5. Check l3-agent was rescheduled
6. Check network connectivity from instance via -----------------Failed
dhcp namespace
7. Run OSTF

Check l3-agent rescheduling after reset non-primary controller vlan

Scenario:
1. Revert snapshot with neutron cluster
2. Create an instance with a key pair
3. Manually reschedule router from primary controller
to another one
4. Reset controller with l3-agent
5. Check l3-agent was rescheduled
6. Check network connectivity from instance via --------------------Failed
dhcp namespace
7. Run OSTF

Actual:
Instance is not acceptable by floating ip

Expected:
ping /ssh to instance by floating ip and open sec groups are success

http://paste.openstack.org/show/492735/

[Tatyanka (tatyana-leontovich)]

https://172.18.160.103/job/9.0.system_test.ubuntu.ha_neutron_destructive_vxlan/65/testReport/junit/%28root%29/neutron_l3_migration_after_reset_vxlan/neutron_l3_migration_after_reset_vxlan/

[Bug Checker Bot (bug-checker)]

(This check performed automatically)
Please, make sure that bug description contains the following sections filled in with the appropriate data related to the bug you are describing:

version

For more detailed information on the contents of each of the listed sections see https://wiki.openstack.org/wiki/Fuel/How_to_contribute#Here_is_how_you_file_a_bug

[Oleg Bondarev (obondarev)]

ovs agent on node-6 (the one that was restarted) failed to start due to:
2016-04-01 00:15:53.545 21019 ERROR neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent [req-24b0cb67-4150-486c-9b66-a89cd9d58f93 - - - - -] Bridge br-floating for physical network physnet1 does not exist. Agent terminated!

Need to investigate why br-floating wasn't created after restart

[Oleg Bondarev (obondarev)]

Looks very similar to https://bugs.launchpad.net/fuel/+bug/1555162

[Atsuko Ito (yottatsa)]

Can I get access to env?

[Ann Taraday (akamyshnikova)]

I have this problem reproducing on the iso 150 and 158. Just restart of the controllers without any other steps leads to described problem. br-floating is not able to be created - error from upstart networking job logs http://paste.openstack.org/show/493037/