resize/migrate in multihost mode doesn't move floating ip

Bug #1053344 reported by Jian Wen on 2012-09-20
26
This bug affects 5 people
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Low
Jian Wen

Bug Description

NAT rules still on source node after confirm-resize

Jian Wen (wenjianhn) on 2012-09-20
Changed in nova:
assignee: nobody → Sina Web Service Dev (sws)
Russell Bryant (russellb) wrote :

Can you provide some more detail in the report? Is the IP moved and rules set up on the other node properly and just the source node doesn't have iptables rules cleaned up?

Changed in nova:
status: New → Incomplete
Jian Wen (wenjianhn) wrote :

Floating ip(s) addr and NAT rules are still on source node.
They should be cleaned on the source node and migrated to the destination node.

Fix proposed to branch: master
Review: https://review.openstack.org/13539

Changed in nova:
assignee: Sina Web Service Dev (sws) → Jian Wen (wenjianhn)
status: Incomplete → In Progress
iopenstack (drdanhe) on 2012-09-27
Changed in nova:
importance: Undecided → Low

Reviewed: https://review.openstack.org/13539
Committed: http://github.com/openstack/nova/commit/df1fb2978c854beb58646406796c2bef2bfb047f
Submitter: Jenkins
Branch: master

commit df1fb2978c854beb58646406796c2bef2bfb047f
Author: Jian Wen <email address hidden>
Date: Fri Sep 21 17:30:18 2012 +0800

    Migrate network of an instance

    In multi_host mode, floating ip(s) addr and NAT rules are still on
    source node after resize/migrate instance. This patch fixes it up by
    adding new methods in network.api to moving them to the destination
    node.

    Also adds the new methods to network/quantumv2/api.py. They do nothing
    but pass for now.

    This patch updates network RPC API to version 1.1

    Fixes bug 1053344

    Change-Id: If9f30050d37831f108ac4a1c8a018d820818f3b6

Changed in nova:
status: In Progress → Fix Committed
Jian Wen (wenjianhn) on 2012-10-25
tags: added: folsom-backport-potential
Thierry Carrez (ttx) on 2012-11-21
Changed in nova:
milestone: none → grizzly-1
status: Fix Committed → Fix Released
Vish Ishaya (vishvananda) wrote :

not really backportable due to rpc api changes.

tags: removed: folsom-backport-potential
Thierry Carrez (ttx) on 2013-04-04
Changed in nova:
milestone: grizzly-1 → 2013.1
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers