[octane] all original floating IPs don't work after upgrade
Bug #1590670 reported by
Pavel Chechetin
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Released
|
High
|
Sergey Abramov | ||
Mitaka |
Fix Released
|
High
|
Arthur Svechnikov |
Bug Description
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
description: | updated |
Changed in fuel: | |
assignee: | nobody → Fuel Octane (fuel-octane-team) |
importance: | Undecided → Medium |
status: | New → Confirmed |
tags: | added: area-python |
Changed in fuel: | |
milestone: | none → 6.0-updates |
Changed in fuel: | |
importance: | Medium → High |
Changed in fuel: | |
milestone: | 6.0-updates → 8.0-updates |
assignee: | Fuel Octane (fuel-octane-team) → Sergey Abramov (sabramov) |
status: | Confirmed → Fix Committed |
milestone: | 8.0-updates → 8.0-mu-3 |
Changed in fuel: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
# Workaround (Tested for 6.1 -> 8.0)
# Execute after "octane upgrade-control"
(new controller)
mysql neutron -e "insert into ml2_flat_ allocations values ('physnet1');" segments set network_ type='flat' ,physical_ network= 'physnet1' where network_id in (select network_id from externalnetworks);"
mysql neutron -e "update ml2_network_
crm resource restart clone_p_ neutron- plugin- openvswitch- agent