[octane] all original floating IPs don't work after upgrade

[Pavel Chechetin]

Detailed bug description:
  All original floating IPs don't work after cutover to the new control-plain.

  In Fuel 8.0 Neutron configuration has undergone significant changes, so old DB state needs additional transformation.

Steps to reproduce:
  Launch VMs
  Assign floating IPs
  Upgrade env (until octane upgrade-control)

Expected results:
  All floating IPs should be pingable

Actual result:
  All floating IPs can't be pinged

Reproducibility:
  Always

Workaround:
  Recreate external network in Neutron and reassign original floating IPs to VMs

Description of the environment:
  Operation system: Ubuntu
  Versions of components: Upgrade from Fuel 6.0 to 8.0
  Network model: Tunnel

[Roman Sokolkov (rsokolkov)]

# Workaround (Tested for 6.1 -> 8.0)

# Execute after "octane upgrade-control"
(new controller)

mysql neutron -e "insert into ml2_flat_allocations values ('physnet1');"
mysql neutron -e "update ml2_network_segments set network_type='flat',physical_network='physnet1' where network_id in (select network_id from externalnetworks);"

crm resource restart clone_p_neutron-plugin-openvswitch-agent

[Ilya Kharin (akscram)]

For stable/8.0 a partial fix was commited: https://review.openstack.org/342674/
For stable/mitaka a merge was made of the next commit: https://review.openstack.org/350558

[Dmitry (dtsapikov)]

Verified on 8.0+mu3

[Vladimir Khlyunev (vkhlyunev)]

299 - verified on 7-9 upgrade